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

[Story] Know which fields are "Not applicable" #287

Open
5 tasks done
natalia-fitzgerald opened this issue Oct 18, 2024 · 1 comment
Open
5 tasks done

[Story] Know which fields are "Not applicable" #287

natalia-fitzgerald opened this issue Oct 18, 2024 · 1 comment
Labels

Comments

@natalia-fitzgerald
Copy link
Contributor

natalia-fitzgerald commented Oct 18, 2024

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

  • 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

Content

  • Add task

Front end

Back end

  • Add task

Data

  • Add task
@natalia-fitzgerald 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
@natalia-fitzgerald
Copy link
Contributor Author

natalia-fitzgerald commented Oct 31, 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"

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

No branches or pull requests

1 participant