Details
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 cancelling the request.
- Scenario
- Given a "Confirm" button on the "Confirm cancellation" modal
- When clicked
- Then the date & time of the cancellation should be recorded for later display and reporting
- Scenario
- Given a "Confirm" button on the "Confirm cancellation" modal
- When clicked
- Then the username of the staff person performing the cancellation should be recorded for later display and reporting (this could be either a staff person or the requester)
- Scenario See Anya's comment below
- Given a "Confirm" button on the "Confirm cancellation" modal
- When clicked
- Then the Cancellation reason and any text entered into the 'Additional information' text box should be recorded for later display and reporting
Out of scope for this story: display of the cancellation reason and additional information on the Close - cancelled request detail screen.
TestRail: Results
Attachments
Issue Links
- blocks
-
UIREQ-92 Requests - Display of actions in Detail and Edit
-
- Draft
-
- is blocked by
-
CIRC-90 Store Request Cancellation Information
-
- Closed
-
-
UIREQ-58 Requests: Cancel
-
- Closed
-
- relates to
-
FOLIO-1291 Add example cancellation reasons to folio-ansible build
-
- Closed
-
-
UIREQ-99 CRUD Request Cancellation Reasons
-
- Closed
-
-
UIREQ-105 Requests - display Cancel information on cancelled requests
-
- Draft
-
-
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
-