Bug 39364 - Items that cannot be renewed should not renew with same due date when selected for renewal
Summary: Items that cannot be renewed should not renew with same due date when selecte...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-17 18:19 UTC by Kristi
Modified: 2025-03-17 18:19 UTC (History)
2 users (show)

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kristi 2025-03-17 18:19:28 UTC
We have certain item types with 0 renewals allowed in their circ rules. 

When a staff member selects these for renewal from a patron's checkout table or they are re-processed via offline circulation, the items are marked as "renewed" with the same due date. 

To replicate:
1. Set up a non-renewable item type in the circ rules. 
2. Check out an item from that item type.
3. From the patron checkouts table in the related patron's account, select all and renew all.
4. The item that could not be renewed will now show a due date of today instead of the future due date it listed previously.


I understand that having the AllowTooManyOverride set to allow may conflict. However, the ideal behavior in the use cases outlined above would be that the item would not attempt to renew, keeping the original due date.