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

[Design] Update UI for Personal Information components #429

Open
21 tasks
nichole-aquino opened this issue Jan 7, 2025 · 0 comments
Open
21 tasks

[Design] Update UI for Personal Information components #429

nichole-aquino opened this issue Jan 7, 2025 · 0 comments
Labels
story User story

Comments

@nichole-aquino
Copy link

Overview

Form builders can easily add/edit Personal Information components (date of birth, Social Security number, email, phone number, gender identity, address)

Context

Reference:

On the build screen:

  • Relabel the question input field to ‘Question text’
  • Widen the question input field
  • For all components, remove the ability to edit the hint labels since these are standard (e.g. For example, 555-11-0000 for SSN)
  • For gender identity, remove the ability to edit the “prefer not to answer” checkbox.

All forms should include this according to USWDS guidance, so builders should not have the ability to edit/remove it. So builders have some awareness of this checkbox, the component will be described as: An input to collect gender identity with an option to select "prefer not to answer.”

Acceptance Criteria

The changes should be made to the following question types:

  • Date of birth
  • Social Security number
  • Email
  • Phone number
  • Gender identity
  • Address

Research Questions

  • Optional: Any initial questions for research

Tasks

Research, design, and engineering work needed to complete the story.

  • [ ]

Definition of done

The "definition of done" ensures our quality standards are met with each bit of user-facing behavior we add. Everything that can be done incrementally should be done incrementally, while the context and details are fresh. If it’s inefficient or “hard” to do so, the team should figure out why and add OPEX/DEVEX backlog items to make it easier and more efficient.

  • Behavior
    • Acceptance criteria met
    • Implementation matches design decisions
  • Documentation
    • ADRs (/documents/adr folder)
    • Relevant README.md(s)
  • Code quality
    • Code refactored for clarity and no design/technical debt
    • Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies; dependency rule followed
    • Code is reviewed by team member
    • Code quality checks passed
  • Security and privacy
    • Automated security and privacy gates passed
  • Testing tasks completed
    • Automated tests pass
    • Unit test coverage of our code >= 90%
  • Build and deploy
    • Build process updated
    • API(s) are versioned
    • Feature toggles created and/or deleted. Document the feature toggle
    • Source code is merged to the main branch

Decisions

  • Optional: Any decisions we've made while working on this story
@nichole-aquino nichole-aquino added the story User story label Jan 7, 2025
@nichole-aquino nichole-aquino changed the title Update UI for Personal Information components [Design] Update UI for Personal Information components Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
story User story
Projects
None yet
Development

No branches or pull requests

1 participant