Details
-
New Feature
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
-
-
Medium
-
XL < 15 days
-
-
Vega
-
-
93
-
R1
-
R4
-
R1
-
R1
-
R1
-
R2
-
R4
-
R2
-
R1
-
R1
-
R1
-
R1
-
R5
-
R1
-
R1
-
R1
Description
This feature was split from UXPROD-82 (Automated Patron Blocks) because two user stories were not completed by the Q2 2020 deadline:
Until MODPATBLK-18 is completed, the following automated patron blocks will not work...
- Maximum number of overdue items
- Maximum number of overdue recalls
- Recall overdue by maximum number of days
The following automated patron blocks are available as of Q2 2020...
- Maximum outstanding fee/fine balance
- Maximum number of items charged out
- Maximum number of lost items
There are Q2 2020 hotfixes needed for the three automated patron blocks implemented as part of Q2 2020 to work properly...
The Maximum outstanding fee/fine balance automated patron block will not work properly until hot fixes are released for the following bugs:
MODPATBLK-26- Automated patron block 'Maximum amount of outstanding fees/fines' does not clear after outstanding fees/fines paidMODPATBLK-27- Blank 'Maximum outstanding fee/fine balance' automated patron block remains when condition removed by libraryMODPATBLK-29- 'Maximum outstanding fee/fine balance' automated patron block not going in effect when it should after changing patron's Patron GroupMODPATBLK-34- Limits for 3 implemented automated patron blocks not working properly
The Maximum number of outstanding lost items automated patron block will not work properly until hot fixes (planned for July) are released for the following bugs:
MODPATBLK-34- Limits for 3 implemented automated patron blocks not working properlyMODPATBLK-38- Automated patron block 'Maximum number of lost items' is not clearing properly - Part 2
The Maximum number of items charged out automated patron block will not work properly until hot fixes (planned for July) are released for the following bugs:
MODPATBLK-34- Limits for 3 implemented automated patron blocks not working properly
There is also a user story impacting all automated patron blocks:
MODPATBLK-35- Add diagnostic GET endpoint for UserSummary objects
TestRail: Results
Attachments
Issue Links
- is defined by
-
MODPATBLK-8 Exclude claim returned items from automated patron block limits
-
- Closed
-
-
MODPATBLK-18 Patron Blocks: use calendar to determine loans overdue status
-
- Closed
-
-
MODPATBLK-52 Do not use calendar for determining overdue blocks
-
- Closed
-
- relates to
-
UXPROD-82 Automated Patron Blocks
-
- Closed
-
-
CIRC-868 Publish an event when item is claimed returned
-
- Closed
-
-
MODFEE-97 Add loan ID to FEE_FINE_BALANCE_CHANGED event
-
- Closed
-
-
UXPROD-2822 Future Patron Blocks: Add automated patron block to block patrons with items overdue x number of days
-
- Closed
-