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 “reject” a submission without deleting it.
Should appear under list of “Rejected” submissions (not disappear).
Need to define what it means for a submission to be rejected (when a submission should be rejected).
Business Rationale:
To have a paper trail of the incorrect/rejected submissions.
This can be brought back to the business to see if it provides actual value to them.
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency |
4 | Parent | |
|
| |
|
|
Technical Details:
Custom feature
Acceptance Criteria:
Define workflow - i.e. where do these submissions go? Back to Ready for Review? Straight back to Submitter? Define workflow for submitter’s perspective.
Might need a mandatory text field providing justification/reason for rejection?
[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 |
|---|