Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
None
-
Small < 3 days
-
Medium
-
Small < 3 days
Description
Purpose: To capture and display actions on a request. Request actions track the history of what has happened to a given request. All requests will have at least one request action (the creation of the request) and as things happen to the request (it is edited, it is cancelled) new actions will be logged against the request.
This story will focus on capturing the request action associated with creating the request.
Scenarios
- Scenario
- Given a the “Create Request” button on the New request screen
- When clicked
- Then the following information should be captured for later display:
- Date and time the request was created
- The nature of the action - “Request created”
- The username of the user that created 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-90 Requests - Capture information during creation
-
- Closed
-
- relates to
-
UX-133 UX: request detail refinement to display username of user who created a request
-
- 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
-