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

[Eng] Add PRA fields to Settings page #494

Open
27 tasks
racheledelman opened this issue Mar 3, 2025 · 0 comments
Open
27 tasks

[Eng] Add PRA fields to Settings page #494

racheledelman opened this issue Mar 3, 2025 · 0 comments
Labels
story User story

Comments

@racheledelman
Copy link

racheledelman commented Mar 3, 2025

Overview

As a builder, I would like to add my OMB tracking number and expiration date to my form, so that I can be in compliance with the PRA.

Image

Context

We should add more PRA support features in the future (proposals in Figma here), but this is the MVP.

Acceptance Criteria

Required outcomes of the story

  • The settings page has a blue background (like the proceeding edit pages) and a white container, 6 columns wide
  • There is a "Settings" title, and a "Paperwork Reduction Act" section
  • Instructions read "Leave this section blank if PRA does not apply to your form."
  • There is a "OMB number" input (accepts numbers and dashes only)
  • There is an "Expiration Date" date input
  • These fields are not required

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
@racheledelman racheledelman added the story User story label Mar 3, 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