Details
-
Story
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
None
-
None
-
-
EPAM-Veg Sprint 129
-
0.5
-
Vega
-
Lotus R1 2022
Description
Purpose: To allow a user to create a title level request
User story statement(s):
As a library staff member,
when viewing a User record, I need to be able to place a new request
- Scenario:
- Given Request permissions https://docs.google.com/spreadsheets/d/1IJnlWvi4k-wFatDNimx9fQ375evHSIIxtGMookHvs-I/edit?usp=sharing
- When I have the permissions below:
- Requests: View, create
- Requests: All permissions
- Requests: View, edit, cancel
- Then the scenarios (3 and on) are true
- Scenario:
- Given Request permissions https://docs.google.com/spreadsheets/d/1IJnlWvi4k-wFatDNimx9fQ375evHSIIxtGMookHvs-I/edit?usp=sharing
- When I do NOT have the permission
- Requests: View, create
- Requests: All permissions
- Requests: View, edit, cancel
- Then I am unable to complete the action in the scenarios below
- Scenario:
- Given Circulation settings
- When "Allow title level requests" AND "Create title level request" selected by default
- Then the following scenarios are true
- Scenario:
- Given a User record in Users
- When I select Create request in the Requests accordion
- Then the New request window loads (
UIREQ-620) with the Create title level request box automatically checked AND with the Requester information already populated
- Scenario:
- Given the Request window
- When I have entered the Title information and I click Save and close
- The title level request is placed and a success toast appears "Request has been successfully created for [input requester name]" AND the user is brought to the Request details
- Scenario:
- Given the Requests window
- When I have entered the Requester information and I click Cancel
- Then a popup appears with the header "Are you sure?" and a message of "There are unsaved changes" with options to Close without saving and Keep editing
- Scenario:
- Given the Cancel popup window
- When I select Close without saving
- Then I am brought to the Requests app (this is how Requests currently works)
- Scenario
- Given the Cancel popup window
- When I select Keep editing
- Then I am brought back to the Requests window from scenario 2
- Scenario:
- Given Circulation settings
- When "Allow title level requests" is selected AND "Create title level request" selected by default is NOT selected
- Then the following scenarios are true
- Scenario:
- Given a User record in Users
- When I select Create request in the Requests accordion
- Then the New request window loads (
UIREQ-620) with the Create title level request box unselected AND with the Requester information already populated
TestRail: Results
Attachments
Issue Links
- defines
-
UIREQ-692 Check TLR on rancher
-
- Closed
-
-
UIREQ-697 Check TLR on rancher
-
- Closed
-
-
UIREQ-720 Check TLR on snapshot
-
- Closed
-
-
UIREQ-721 Check TLR on rancher
-
- Closed
-
-
UXPROD-1796 Title Level Requests Complete (part 1)
-
- Closed
-
- relates to
-
UIREQ-656 Spike: Create a title level request checkbox
-
- Closed
-
-
UIREQ-657 Spike: Create a title level request checkbox
-
- Closed
-