You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
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):
See full ticket and images here: FECFILE-1909
The text was updated successfully, but these errors were encountered: