-
Notifications
You must be signed in to change notification settings - Fork 4
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
Create Group F Transaction Screen (PAC JF Transfer Memo) #327
Comments
@AureliaKhorsand |
Consideration for FEC discussion: If the Parent Transaction name changes after the sub-transaction ticket has been saved, the Contribution Purpose Description note will still display the old name. This is an edge case, but we can prevent this issue a few ways. This is a discussion topic for the 7/5 requirements meeting and not in scope of this ticket. |
Requested some changes in the fecfile-app and fecfile-validate repos for this ticket. Sending to In Progress |
Returned to in-progress "Date Field" not showing "Required Field". This is broken in this ticket, as it worked in Sprint 9. QA was not aware of any defect being written on this ticket. |
The date field not showing that it is required is not isolated to this ticket, and correcting this error has its own ticket |
Note: Wireframe and Acceptance showed:
After verifying requirements CONTRIBUTOR FEC ID (A/N-10, Required) should be A/N-9. |
QA reviewed and verified Group F Transaction Screen using JF Transfers. Test Case/Test Script attached showing ticket “PASS”. QA review completed. Moved to Stage Ready. |
Business Reason
As a Committee Administrator, I will be able to enter a sub-transaction under "JF Transfers" on Schedule A of a Form 3X report so that I can accurately report on my committee's transactions.
NOTE: This is a "child" transaction that will be associated with a parent transaction.
Acceptance Criteria
Given I am a Committee Administrator
And I am editing a JF Transfer transaction on an open report
Then I will have the option to enter the following sub-transaction:
And I will be required to enter the following information (unless otherwise noted):
Contributor
CONTRIBUTOR TYPE (Read-only)
Field description in API: ENTITY TYPE
Data field: COMMITTEE
CONTRIBUTOR COMMITTEE (A/N-200, Required)
Field description in API: CONTRIBUTOR ORGANIZATION NAME
Data field: textbox
CONTRIBUTOR FEC ID (A/N-9, Required)
Field description in API: DONOR COMMITTEE FEC ID
Data field: textbox
With the ID in the following format: "CXXXXXXXX" where X is a numeric value (C, then 8 numbers)
FEC ID IS A STOP-GAP UNTIL THE LOOKUP IS IN PLACE
Address
STREET ADDRESS (A/N-34, Required)
Field description in API: CONTRIBUTOR STREET 1
Data field: textbox
APARTMENT, SUITE, ETC. (A/N-34, Optional)
Field description in API: CONTRIBUTOR STREET 2
Data field: textbox
CITY (A/N-30, Required)
Field description in API: CONTRIBUTOR CITY
Data field: textbox
STATE/PROVINCE (ALPHA-2, Required)
Field description in API: CONTRIBUTOR STATE
Data field: Dropdown
Dropdown options: States without military
https://docs.google.com/spreadsheets/d/17YmnaZgqvFOUyv4-Qknd8ikHe8o9LoDb/edit#gid=494776297
ZIP/POSTAL CODE (A/N-9, Required)
Field description in API: CONTRIBUTOR ZIP
Data field: textbox
Contribution
DATE RECEIVED (NUM-8…YYYYMMDD, Required)
Field description in API: CONTRIBUTION DATE
Data field: Date picker
MEMO ITEM (A/N-1, Optional)
Field description in API: MEMO CODE
Data field: Checkbox
CONTRIBUTION AMOUNT (AMT-12, Required)
Field description in API: CONTRIBUTION AMOUNT
Data field: textbox
CONTRIBUTION AGGREGATE (AMT-12, Required)
Field description in API: CONTRIBUTION AGGREGATE
Data field: textbox (FOR NOW it will say $0.00)
Additional information
CONTRIBUTION PURPOSE DESCRIPTION (Read-only)
Field description in API: RECEIPT DESCRIPTION
Data field: multi-line textbox that must read "JF Memo: XX", where XX is auto-populated with the name of the committee entered in parent transaction JF_TRAN COL SEQ 8
NOTE OR MEMO TEXT (A/N-100, Optional)
Field description in API: MEMO TEXT/DESCRIPTION
Data field: multi-line textbox
Then I will be able to:
Dev Note
See Schedule A spec here.
See spec here.
QA Notes
null
DEV Notes
null
Design
null
See full ticket and images here: FECFILE-1168
The text was updated successfully, but these errors were encountered: