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
Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.
As a filer, I want to know which financial institution data fields do not pertain to my financial institution ("Not applicable") or are missing required data values, so that I can ensure that my financial institution is accurate and complete.
Acceptance criteria
Given a user is on the view your financial institution profile page, when they navigate to different sections of the page, then they see that fields are either populated or "Not applicable."
General approach
All fields, other than the following exceptions, will be populated or "Not applicable"
Exception: TIN will always be either populated or blank.
Exception: Type of financial institution will always be populated or blank.
Technical tasks
Team members should create technical tasks and add links (below) prior to sprint planning.
UX
Write initial user story
Review against task analysis for accuracy and relevance (if applicable)
Map story issue to the task analysis (if applicable)
natalia-fitzgerald
changed the title
[Story] Start with verb that describes user action (pull from the "I want to" part of the user story)
[Story] Know which fields are "Not applicable"
Oct 18, 2024
@dan-padgett@angelcardoz Here, I proposed changing the acceptance criteria for this story to show "Not provided" instead of blank for fields that are user provided, that appear on the View/Update financial institution profile pages, and where the user has not yet provided the information. This includes TIN and Type of financial institution. Can we move forward with this adjustment?
This would mean editing the text above to:
Exception: TIN will always be either populated or show "Not provided"
Exception: Type of financial institution will be populated or show "Not provided"
Epic
Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.
User story
Acceptance criteria
General approach
Technical tasks
Team members should create technical tasks and add links (below) prior to sprint planning.
UX
Content
Front end
Back end
Data
The text was updated successfully, but these errors were encountered: