Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
User Story Description:
| Anchor | ||||
|---|---|---|---|---|
|
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 they needeach 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 |
1 |
|
|
2 |
|
|
344 | Child | |
43 | Child | |
| 4 | |
|
|
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
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|