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
Note to design: This ticket originally was to re-add the committee lookup, however see the comment below for notes from 3/4/25 requirements session.
Business Reason
As a user, I will be able to enter COMMITTEE ID or COMMITTEE NAME on the Account Creation page to search for my committee to add (with a LOOKUP) in the production application
Acceptance Criteria
Given the user has selected "Create a new committee account" when they click this button then there will be a lookup field for them to enter the Committee ID or name
and when they press enter or click to search the system will:
show a list of committees registered on fec.gov
Given the user has entered an incorrect Committee ID or a Committee ID that cannot be found in the system
when they press enter or click to search
then the system will inform them there was an issue creating the committee, and they can either:
enter a new Committee ID
go back
QA Notes
DEV Notes
Design
h2. Wireframe for lookup (examples)
!1509-System to allow ONLY Committee ID selection on the Account creation page and remove the lookup for Committee Name.png|width=1365,height=884,alt="1509-System to allow ONLY Committee ID selection on the Account creation page and remove the lookup for Committee Name.png"!
exalate-issue-syncbot
changed the title
System to allow ONLY Committee ID selection on the Account creation page and remove the lookup for Committee Name
System to re-add the lookup for Committee Name in production
Feb 27, 2025
akhorsand commented: Requirements discussion on 3/4/25: This functionality is not prioritized for production launch in June 2025. However, the usability of entering a committee ID at account creation is still something we’d like to consider. Potential future solutions include:
We could pull both processed and raw data into a lookup, but this would still leave the problem of potentially offensive names. However, since it's production, it would fall under "false and fictitious filing" and may be less of an issue.
We can update the message if a committee account cannot be created to indicate the user should double check they typed it correctly.
This ticket will remain with the design team for analysis.
exalate-issue-syncbot
changed the title
System to re-add the lookup for Committee Name in production
[UX] Improve usability of committee account search in account creation
Mar 4, 2025
Note to design: This ticket originally was to re-add the committee lookup, however see the comment below for notes from 3/4/25 requirements session.
Business Reason
As a user, I will be able to enter COMMITTEE ID or COMMITTEE NAME on the Account Creation page to search for my committee to add (with a LOOKUP) in the production application
Acceptance Criteria
Given the user has selected "Create a new committee account"
when they click this button
then there will be a lookup field for them to enter the Committee ID or name
and when they press enter or click to search the system will:
Given the user has entered an incorrect Committee ID or a Committee ID that cannot be found in the system
when they press enter or click to search
then the system will inform them there was an issue creating the committee, and they can either:
QA Notes
DEV Notes
Design
h2. Wireframe for lookup (examples)
!1509-System to allow ONLY Committee ID selection on the Account creation page and remove the lookup for Committee Name.png|width=1365,height=884,alt="1509-System to allow ONLY Committee ID selection on the Account creation page and remove the lookup for Committee Name.png"!
!1509-S2 (895b59bd-f047-426c-9e4f-e6e0d093d14d).png|width=1365,height=884,alt="1509-S2.png"!
!1509-S3 (11ea1c46-47ec-45f3-99a8-eb1010b794a6).png|width=50%,alt="1509-S3.png"!
!Screenshot 2024-10-02 at 1.56.48 PM.png|width=592,height=331,alt="Screenshot 2024-10-02 at 1.56.48 PM.png"!
See full ticket and images here: FECFILE-2060
The text was updated successfully, but these errors were encountered: