Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
-
None
-
Large < 10 days
-
Low
-
This estimate assumes we already capture date & time
-
Small < 3 days
Description
Purpose: To capture and display metadata for actions taken on a request. Request actions track the history of what has happened to a given request. All requests will have at least one metadata entry (the creation of the request) and as things happen to the request (it is edited, it is cancelled) new metadata entries will be logged.
This story will focus on capturing metadata when the request is edited.
Scenarios
- Scenario
- Given a the “Update Request” button on the Edit request screen
- When clicked
- Then the following information should be captured for later display:
- Date and time the edit was performed
- The username of the user that edited the request (this could be either a staff person or the requester)
TestRail: Results
Attachments
Issue Links
- blocks
-
UIREQ-92
Requests - Display of actions in Detail and Edit
-
- Draft
-
- is duplicated by
-
UIREQ-91
Requests - Capture information during edit
-
- Closed
-
- relates to
-
UIREQ-101
Requests - capture action information during edit
-
- Closed
-
-
UX-186
UX: Request Actions section mockups
-
- Closed
-
-
UIREQ-86
Request details: record last update info not formatted properly
-
- Closed
-
-
UXPROD-1056 Requests: track and display all changes to a request
-
- Draft
-