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

Simple Report Workflow #484

Open
20 tasks
patriciarussellCAS opened this issue Dec 30, 2024 · 0 comments
Open
20 tasks

Simple Report Workflow #484

patriciarussellCAS opened this issue Dec 30, 2024 · 0 comments
Labels
Backlog Refinement Tickets that require further refinement User Story A User Story issue type

Comments

@patriciarussellCAS
Copy link

patriciarussellCAS commented Dec 30, 2024

Description:

There may be situations where a Reporting or Regulated Operation will need to fill out a Simple Report instead of an Annual Report. This ticket is to capture the work required to build the simple report workflow.

Simple Report Workflow Wireframes

There is a separate ticket for the simple report's Final Review Page #400

Acceptance Criteria:

Given that I am an Industry User who needs to fill out a simple report
When I am on the Review Operation Information Page and select "Simple Report" for report type
Then I am shown the simple report workflow (see figma link above)

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:

@patriciarussellCAS patriciarussellCAS added Backlog Refinement Tickets that require further refinement User Story A User Story issue type labels Dec 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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