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

[Bug 32489] New: Add check out date, number of renewals, numbers of overdue days in list of overdues
by bugzilla-daemon＠bugs.koha-community.org 14 Jun '26

14 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32489 Bug ID: 32489 Summary: Add check out date, number of renewals, numbers of overdue days in list of overdues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In circ/overdue.pl it could be useful to add for each line - the check out date - the number of renewals - the number of overdue days (today - due date) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 27105] New: Add checkout notes from staff client
by bugzilla-daemon＠bugs.koha-community.org 13 Jun '26

13 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27105 Bug ID: 27105 Summary: Add checkout notes from staff client Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com AllowCheckoutNotes allows patrons to add notes for a specific checkout from OPAC. It could be useful we could have the same feature on Staff client. Librarians could add some useful informations for checking (annotated or highlighted text before the checkout, book already damaged, needs a new label after the return, etc.). A good feature to have less litigation with patrons when checking books with some problems ! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 30680] New: Behavior due to MARC Overlay Rules should be reflected in Diff view when staging MARC batches for import
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30680 Bug ID: 30680 Summary: Behavior due to MARC Overlay Rules should be reflected in Diff view when staging MARC batches for import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 14957 To recreate: - create a rule on /marc-overlay-rules.pl to protect the 050 tag when staging for MARC import - export a record from your collection and remove the 050 outside of Koha - reimport that record, matching your incoming record to the one already in your collection - confirm the Diff view on manage-marc-import.pl says the 050 will be deleted - complete import, confirm the 050 was retained We should somehow denote when a field will not be impacted due to an overlay rule. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 [Bug 14957] Write protecting MARC fields based on source of import -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 38527] New: Add logging of reports (created, run, changed and deleted)
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38527 Bug ID: 38527 Summary: Add logging of reports (created, run, changed and deleted) Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: inkeri.hakulinen+bugz(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org For GDPR reasons it would be good to have Koha to log the use of reports. I suggest that the log should include data about -who created which report and when and what the sql was -who run which report and when and what the sql was (the actual sql that was run, since sometimes you choose / fill in some parameters when you run the report) -who changed which report and when and how the sql was changed (before & after) -who deleted which report and when and what the sql was -probably also the updates to the report descriptions would be good to log? However, the results of the reports should not be saved into logs, of course. This addition would bring transparency about the use of the reports. That would be important for preventing misuse of customer data. Now Koha doesn't collect so detailed data, and it would be easy to collect customer data without a trace in the logs. This data would of course be helpful also in cases, when someone accidentally changes a report so that it doesn't work anymore. You could detect the old report from the logs. Also this would help solving crashes that happened due to running too heavy reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 33827] New: The option to skip bundle verification at checkin should be syspref driven
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33827 Bug ID: 33827 Summary: The option to skip bundle verification at checkin should be syspref driven Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: caroline.cyr-la-rose(a)inlibro.com, gmcharlt(a)gmail.com, jacob.omara(a)ptfs-europe.com, julian.maurice(a)biblibre.com, kyle.m.hall(a)gmail.com, kyle(a)bywatersolutions.com, martin.renvoize(a)ptfs-europe.com Depends on: 28854, 31615 Blocks: 32802 Some libraries do not want to allow unverified check-ins of bundle sets. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28854 [Bug 28854] Add ability to create bundles of items for circulation https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31615 [Bug 31615] Allow checkin of items bundles without verifying their contents https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32802 [Bug 32802] Bundle handling JS should be moved to an asset -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[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