Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
User Story description:
Anchor | ||||
---|---|---|---|---|
|
As a reviewer, I want to be able to mark a submission as completed.
Define Completed as reviewed + approved What this could look like →
Possible Workflow
Scenario 1. When a submission completes the reviewal process and is ultimately approved, the reviewer (confirm if only the reviewer ) clicks “approved“ and submission appears under “completed” status .
Business Rationale:
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency | ||||
1 | As a reviewer I want to be able to consult the 4 | #4: (Reviewer) Consult assigned forms/files I am assigned to | Parent | 2 | As a reviewer I want to be able to re-assign a submission | Child |
3 |
| 4 | ||||
|
|
Technical Details:
OOTB feature
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 | ||
2 | ||
3 | ||
4 |
| |
5 |
|
Prototype/Mockups
Provide high fidelity prototype or mock-up
Out of Scope:
Contact(s):
Table of Contents
Table of Contents |
---|