Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow user to link a transaction to a report #2458

Open
exalate-issue-sync bot opened this issue Dec 20, 2024 · 1 comment
Open

Allow user to link a transaction to a report #2458

exalate-issue-sync bot opened this issue Dec 20, 2024 · 1 comment
Assignees

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Dec 20, 2024

Business Reason

As a user, I would like to be able to manually link a transaction (such as one created in https://fecgov.atlassian.net/browse/FECFILE-1826) to an existing report, so that I can report my transactions.

Acceptance criteria

Given a transaction not linked to a report

When I [design TBD]

Then the transaction is linked to the report selected [note: should we also link tier 2 and tier 3 when the tier 1 is linked?]

And the transaction can be viewed when selecting the report in Manage reports page

QA Notes

null

DEV Notes

null

Design

Things to think about in design (which might need additional tickets):

  • ‘Related’ transactions would also be linked (should we message users?)
  • If we link a transaction with dates outside of the report dates, should flag this to user

See full ticket and images here: FECFILE-1909

Copy link
Author

gregg.moreland commented: [~accountid:61b0b42cd5986c006a9e1c94] If we link a Tier 1 transaction, should we automatically link all related transactions? Not just tier 2 and tier 3, but also, for example, if a loan is created outside of the report, should we automatically link related transactions? My thoughts are yes on all. Something to keep in mind for design and for dev’s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants