Details
-
Story
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
None
-
-
Core: F - Sprint 94
-
1
-
Prokopovych
Description
SAME SCENARIOS AS WITH DECLARED LOST
Purpose: Prevent user from creating requests of any type (page, request, hold) when an item has the status Aged to lost.
Scenarios:
- Scenario
- Given an item with the item status Aged to lost
- When the item is entered in the New Request form
- Then display the following modal:
- Title: Item cannot be requested
- <Title of item> (<material type of item>) (Barcode: <barcode of item>) has the item status Aged to lost and cannot be requested.
- Controls: Close
- Scenario
- Given the Item cannot be requested modal from scenario 1
- When the user clicks Close
- Then under Request type on the New request form, display "No request types available for selected item"
- Scenario
- Given an item with the item status Aged to lost in the New Request form
- When the user clicks Save and Close on the request form
- Then:
- Do not save the request
- Display the Item cannot be requested modal from scenario 1
Notes:
- Modeled after similar behavior when patron is blocked from requesting
- Attached wireframe is for preventing requests when status is Withdrawn, not Aged to lost, but should be similar
TestRail: Results
Attachments
Issue Links
- clones
-
CIRC-614 Back end: Declared lost item: prevent all request types
-
- Closed
-
- defines
-
UXPROD-87 Loan: Aged to Lost using SET COST
-
- Closed
-
- has to be finished together with
-
UIREQ-429 Aged to lost: Prevent all request types
-
- Closed
-
- is blocked by
-
CIRC-737 Aged to lost: Automatically age overdue items to lost - SET COST
-
- Closed
-
-
CIRCSTORE-198 Backend: Automatically age overdue items to lost
-
- Closed
-
-
CIRCSTORE-199 Backend: Add "agedToLostDelayedBilling" property to loan schema
-
- Closed
-