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 6 Current »

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:

top page

Enable visibility into who made what changes and when. Does not provide the reason why - TBC if needed at all by the business areas.

Dependencies:

top page

[List potential dependencies with other User Stories or Tasks]

#

Task or User Story

Type of Dependency

44

#44: (Admin) Restore a form to a previous version

 Child

43

 #43: (Admin) Form Versioning

 Child

 

 

 

 

Technical Details:

top page

OOTB

Acceptance Criteria:

top page

[List the Acceptance Criteria]

#

Description

Notes

1

 

 

2

 

 

3

 

 

4

 

 

5

 

 

Prototype/Mockups

top page

Provide high fidelity prototype or mockup

Out of Scope:

top page

Contact(s):

top page

Table of Contents

  • No labels