/
#45: History of a form to be stored
#45: History of a form to be stored
- Miranda Stewart
Owned by Miranda Stewart
User Story Description:
As an Admin I want the edit history of a form to be stored. This would include history of status for a given submission.
Will have to confirm with the client what level of detail each business area needs. In the current instance of CHEFS, only shows the Time, User & Version?
Business Rationale:
Enable visibility into who made what changes and when. Provides visibility into where submissions are in the workflow as well.
Does not provide the reason why - TBC if needed at all by the business areas.
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency |
44 | Child | |
43 | Child | |
|
|
|
|
|
|
Technical Details:
OOTB
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
5 |
|
|
Prototype/Mockups
Provide high fidelity prototype or mockup
Out of Scope:
Contact(s):
Table of Contents
, multiple selections available,
Related content
FORMS-214: (Submitter) generate new submission from previous one
FORMS-214: (Submitter) generate new submission from previous one
Read with this
#4: (Reviewer) Consult assigned forms/files
#4: (Reviewer) Consult assigned forms/files
Read with this
#49: (Submitter) Grouping Forms
#49: (Submitter) Grouping Forms
Read with this
Epic #1: Generic Form Design
Epic #1: Generic Form Design
Read with this