June 2025 - Koha-bugs - lists.koha-community.org

[Bug 39218] New: Need separate DefaultHoldPickupLocation setting for Holds placed via the OPAC
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39218 Bug ID: 39218 Summary: Need separate DefaultHoldPickupLocation setting for Holds placed via the OPAC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: jeremy.evans(a)ukhsa.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We would like to be able to set a DefaultHoldPickupLocation default option for holds placed via the OPAC. We want OPAC holds to default to the item home library - most of our users are remote users not based on the same sites as the stock. The items are posted out to them from the holding library. The default site pick up selection currently shows in alphabetical order of site so most holds default to the the first site on the list even if it does not hold the book being requested. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 25966] New: Renewal of lost item generates overdue fine
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25966 Bug ID: 25966 Summary: Renewal of lost item generates overdue fine Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If an item is both overdue and lost, renewal of that item will generate fines. This behavior is inconsistent with the behavior of the fines cron, which explicitly excludes lost items from fines. I expect there are libraries that prefer the current behavior but also libraries that would rather not generate overdue fines on renewal of lost items. So perhaps a system preference is in order? Do/Don't charge fines on renewal of lost items? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 22557] New: Delayed authority merges looses the user in the action_logs
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22557 Bug ID: 22557 Summary: Delayed authority merges looses the user in the action_logs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 21653] New: add koha-cronlogaction script, which will call C4/Log::cronlogaction with the remaining command line arguments set as "info" in the logs.
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21653 Bug ID: 21653 Summary: add koha-cronlogaction script, which will call C4/Log::cronlogaction with the remaining command line arguments set as "info" in the logs. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Sometimes it is useful for administrators to make changes that affect libraries, but which would not otherwise be logged -- this could be called from a shell script, and would give clues to any changes made within the script. usage: koha-cronlogaction INSTANCE-NAME "text to be added to logs" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 37626] New: Add logging for when an acquisition basket is deleted
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37626 Bug ID: 37626 Summary: Add logging for when an acquisition basket is deleted Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org If the AcquisitionLog is set to "log" we log all kinds of activities on baskets: create, modify, close, re-open, but we don't log when a basket is deleted. Deleting a basket will also delete the order lines and optionally records and items. So it's important to understand what happened in case something goes wrong. The button to delete a basket is available on open baskets in the top toolbar on the basket summary page. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 34771] New: Add Logging option for ERM Licenses
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34771 Bug ID: 34771 Summary: Add Logging option for ERM Licenses Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: ian(a)bywatersolutions.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Requirements: * a syspref in the Logging section, LicensesLog, to toggle the feature - default to false * On creation of a License log a 'Create' action with C4::Log::logaction() * On update of a License, log an 'Update' action, including which fields are changed -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 34770] New: Add Logging option for ERM Agreements
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34770 Bug ID: 34770 Summary: Add Logging option for ERM Agreements Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: ian(a)bywatersolutions.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Requirements: * a syspref in the Logging section, AgreementsLog, to toggle the feature - default to false * On creation of an Agreement, log a 'Create' action with C4::Log::logaction() * On update of an Agreement, log an 'Update' action, including which fields are changed -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 39910] New: Add script to columns view of action logs
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39910 Bug ID: 39910 Summary: Add script to columns view of action logs Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Since 22.11 when action logs began capturing the script creating a change, it would be fabulous to have that visible as a column instead of something only accessible via report. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 38805] New: Add bookings logging
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38805 Bug ID: 38805 Summary: Add bookings logging Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the addition of new timestamp fields with bookings via bug 37592, having those actions logged in action logs would make it more meaningful/visible for troubleshooting. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 37884] New: Interface in action logs for renewals is OPAC if the previous renewal was in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37884 Bug ID: 37884 Summary: Interface in action logs for renewals is OPAC if the previous renewal was in the OPAC Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org When you do a renewal in the staff interface, and the previous renewal was in the OPAC, the actions logs will say it was done in the OPAC. To recreate: 1. Enable RenewalLog 2. Check out an item to patron A 3. Check out another item to patron B 4. Log in the the OPAC as patron A and renew the checkout 5. In the staff interface, renew the checkout for patron B 6. Go to Tools > Log Viewer 7. Check the Circulation module and click OK --> Both renewals have the interface "OPAC" It seems to be a cookie thing maybe? If I do the OPAC renewal in a private browser window, it's ok. I realize this is unlikely to happen in real life, I was trying to create log entries for the manual. But I don't know enough to know if this is a symptom of a bigger problem or not, so I figured I'd report it... -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2