Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

User Story description:

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:

top page

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:

top page

[List potential dependencies with other User Stories or Tasks]

#

Task or User Story

Type of Dependency

4

#4: (Reviewer) Consult assigned forms/files

Parent

 

 

 

 

 

Technical Details:

top page

Custom feature

Acceptance Criteria:

top page

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

top page

Provide high fidelity prototype or mock-up

Out of Scope:

top page

Contact(s):

top page

Table of Contents

  • No labels