Bug 36631 - longoverdue maxdays should be configurable in interface
Summary: longoverdue maxdays should be configurable in interface
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Command-line Utilities (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-17 21:20 UTC by Evelyn Hartline
Modified: 2024-04-17 21:20 UTC (History)
1 user (show)

See Also:
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 Evelyn Hartline 2024-04-17 21:20:59 UTC
If a library sets the DefaultLongoverdueDays syspref to a value greater than the maxdays default (366) without explicitly setting a larger maxdays value in the cron, longoverdue items will not be correctly processed. 

Being able to override the maxdays default of 366 with something like a configurable DefaultLongoverdueMaxDays value in the interface would make sure that the default is both known and taken into account by the library staff, as well as making it simpler for library staff to configure the longoverdue settings without having to have access to the command line.