#45: History of a form to be stored
- 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
Â
Â