Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Duplicate
-
None
-
None
-
EPAM-Veg Sprint 136
-
1
-
Vega
-
Lotus (R1 2022) Bug Fix
-
Implementation coding issue
Description
Note: This may be a P1 for Chicago, given they age recalled items to lost faster than regular overdue items.
Overview:
Steps to Reproduce:
- Log into Lotus BugFest as an admin user
- Create a Lost Item Fee Policy that looks like this...
- Check out an item to a patron that uses the new Lost Item Fee Policy that you created above
- Have another patron do a recall on the item checked out above
Expected Results:
Per the Lost Item Fee Policy, one minute after the recalled item is overdue it is eligible to be aged to lost. I expected the recalled item to be aged to lost within one hour, given the process runs on a schedule.
Actual Results:
Recalled items were aged to lost 3 hours after they were overdue, which is following the settings for regular overdue items, not recalled items. Here is what the Opens Loans page looked like for Rita Recall after the items were aged to lost...
Additional Information:
If you have a Lost Item Fee Policy that looks like this (regular overdue items do not aged to lost at all)...
...your recalled items will never age to lost, as shown below...
Interested parties:
hollyolepm
TestRail: Results
Attachments
Issue Links
- is cloned by
-
UIU-2566 "Maximum number of overdue recalls" and "Recall overdue by maximum number of days" automated patron blocks not being enforced
-
- Closed
-