Export - CSV (All fields)
Export - CSV (Current fields)
CIRC-1610
TLR: Item assigned to recall should not be renewable
Rolling due date loan policy with fixed due date schedule(due date limit) fails when the schedule range begins after the checkout date
Date parsing in mod-circulation does not handle loanDate/dueDate without timezone information but allows saving loans without that information
TLR (pages) aren't being fulfilled when there is an available non-requestable item at the chosen service point
500 Error When Placing TLR/Instance Requests via mod-patron When There Are "Available" but not Pageable Items
When checking out an item, a server error appears
The queue in requests breaks if we replaced an item in the request
Platform builds broken: Incompatible version for module folio_requests-7.0.100000386 interface circulation - Need 12.0 have 11.0
Cannot Move Requests Between Items (Queue Position Conflict)
When TLR feature is disabled, assign ILR during instance level requests creation
"closed-filled" requests have "Request expiration" notices sent
Request statuses not following correct path when title and item level requests are placed
Duplicate permission defined in mod-circulation module descriptor
Recall Request Not Triggering Recall Requested Action on Loan in Bugfest
Due dates not changed according to loan policy rules for recalls in Lotus bugfest
Wrong calculation of the due date when there is a an exceptional closed period
Overdue and Courtesy notices generated but not sent if loan has been renewed
SPIKE: Investigate wrong calculation of the due date when there is a an exceptional closed period
Not all loans are anonymized if there are > 5000 closed loans (with userid)
Aged to lost process need to process ACTUAL COST items if there is a LOST ITEM PROCESSING FEE
On SNAPSHOT, ACTUAL COST lost items are being closed as "Lost and paid" before "Lost item fee (actual cost)" has been billed
Overdue fines not charged if item due before library closes but returned after library has been closed
Claimed returned item appears to be checked in, but user not asked how to resolve the claim plus not actually marked as returned on Open Loans
Receive error when attempting to check-in items on Lotus BugFest
BACKEND - Recieve "HTTP 500 Internal Server Error" on every book checked out
Without Calendar permissions, check-ins do not calculate overdues
Not all loans are anonymized if there are > 5000 closed loans (with userid)
DELETE /circulation/loans with query params trigger bulk DELETE /circulation/loans
cross-tenant policy id causing 500 errors during circ. transactions
[Nolana BugFix] cross-tenant policy id causing 500 errors during circ. transactions
500 error is shown after the item checkout
[Orchid] Calendar timetable is absent for requested date
Calendar timetable is absent for requested date
Notice not sending for notice trigger = Item recalled
TLR: user able to place title level request when TLR is not enabled
A page request placed on item remains open despite the item being now on loan to another patron
IF TLR with no existing item OR with request type = Hold, then item tokens that are linked to instance are not populated (immediate notices)
TLR: renewals on holds allowed regardless of loan policy
TLR: Recalls not fulfilling correctly
NPE when creating TLR Recall for instance without an open loan
POST /circulation/requests requires more fields than before
Add itemLimit parameter to the item limit error
Broken scheduled notices are blocking notice delivery
When checking in an item, a server error
Scheduled Notices Sent After Loan Marked Claimed Returned
Check-out and multiple loans renewal workflow performance is not good for users with large number of loans.
When Creating a Title Level Request (basic TLR) For an Instance with More than 10 Associated Items, Not All Items are Considered to Fill the Request
Missing module permissions for POST to /circulation/requests
Unable to Place Recalls via Instance Hold Endpoint (/circulation/requests/instances) When Item is Checked out with a Fixed Due Date Schedule
Choose request level and request type when creating a request