Details
-
Bug
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
None
-
-
Vega
-
R2 2021 Hot Fix #7
-
Yes
-
Approved via release_bug_triage Slack channel.
-
-
Cornell, Spokane Public Libraries, TAMU, University of Chicago
-
TBD
Description
Overview: Patron automatic blocks are aged to lost, then the patron renews them- but the block is not removed
Steps to Reproduce:
- Patron checks out item
- a trigger to automatic block happens
- the item ages to lost
- patron ties to renew - but can't so it is overriden to renew
- the automatic block is not removed
Expected Results: the block is removed
Actual Results: the block remains
Additional Information:
URL:
Interested parties:
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-3409 Vega - Lotus Enhancements/Bugfixes/Tech Debt
-
- Closed
-
- has to be done after
-
MODPATBLK-110 Reproduce, investigate and estimate MODPATBLK-109
-
- Closed
-
- relates to
-
MODAUD-93 Error logging is missing key information
-
- Closed
-
-
MODPATBLK-112 Juniper: Automated Block for Max Amount Owed Not Removed When Aged to Lost Item Returned
-
- Closed
-
-
MODPATBLK-116 ITEM_AGED_TO_LOST events not cleared before synchronization
-
- Closed
-
-
MODPATBLK-119 SPIKE - Investigate patron blocks issues - MODPATBLK-109
-
- Closed
-
-
MODPATBLK-111 Kiwi: automatic block 'Maximum lost items" not removed after item renewed for patron
-
- Closed
-
- mentioned in
-
Page Loading...