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 request a revision for a given submission.
Request for revision functionality involves clicking on “revise” button, which returns it to the submitter.
Will this request be communicated via email?
Business Rationale:
Request for revision functionality involves clicking “reject” when in review state? If enough information is missing/inaccurate in a given submission, the reviewer should be able to reject / send back the submission to the submitter so they can review, make the necessary changes and send it back to the reviewer for another review.
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 |
3 |
|
| ||
4 |
|
|
Technical Details:
OOTB
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 |
---|