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

Supplementary Report - Create a Review Changes page #479

Open
23 tasks
zoeyli-46 opened this issue Dec 24, 2024 · 1 comment
Open
23 tasks

Supplementary Report - Create a Review Changes page #479

zoeyli-46 opened this issue Dec 24, 2024 · 1 comment
Labels
attn: Developer Blocked issue, requires dev attention Backlog Refinement Tickets that require further refinement User Story A User Story issue type

Comments

@zoeyli-46
Copy link

Description:

There is a new Review Changes page in supplementary report mode, which comes before the Final Review page

Acceptance Criteria:

Given I am on the attachments page
When I click continue
Then I am brought to the Review Changes page

Given I am on the Review Changes page, I see the following:

  • the page section and fields that were changed, in view-only mode
  • 1 editable text box "reason for edits" (mandatory field)

Given that I have filled out the mandatory "reason for edits",
Then the disabled continue button gets enabled and this field gets appended on to the end of the final review page.

Development Checklist:

  • Checklist item
  • Checklist item
  • Checklist item
  • Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

  • User story is included
  • User role and type are identified
  • Acceptance criteria are included
  • Wireframes are included (if required)
  • Design / Solution is accepted by Product Owner
  • Dependencies are identified (technical, business, regulatory/policy)
  • Story has been estimated (under 13 pts)

Definition of Done (Note: If any of these points are not applicable, mark N/A)

  • Acceptance criteria are tested by the CI pipeline
  • UI meets accessibility requirements
  • Configuration changes are documented, documentation and designs are updated
  • Passes code peer-review
  • Passes QA of Acceptance Criteria with verification in Dev and Test
  • Ticket is ready to be merged to main branch
  • Can be demoed in Sprint Review
  • Bugs or future work cards are identified and created
  • Reviewed and approved by Product Owner

Blocked By/Blocking

Notes:

@zoeyli-46 zoeyli-46 added Backlog Refinement Tickets that require further refinement User Story A User Story issue type attn: Developer Blocked issue, requires dev attention labels Dec 24, 2024
@zoeyli-46
Copy link
Author

@patriciarussellCAS new supplementary report ticket for the Review Changes page

@zoeyli-46 zoeyli-46 changed the title Supplementary Report: Create a Review Changes page Supplementary Report - Create a Review Changes page Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
attn: Developer Blocked issue, requires dev attention Backlog Refinement Tickets that require further refinement User Story A User Story issue type
Projects
None yet
Development

No branches or pull requests

1 participant