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

[Bug 36135] New: Add tool to batch edit pick up dates of holds
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '26

21 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36135 Bug ID: 36135 Summary: Add tool to batch edit pick up dates of holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are sometimes situations where libraries have to extend their holds pick up dates. We should at same kind of tool for this like "Batch extend due dates". However criteria for dates to extend can be complicated (we've excluded e.g. items with specific state, holds with found status, items on transfer to specific library). So rather than using predefined criteria for holds to edit (at least for the start), tool should have option to upload file of SQL query results. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 270

[Bug 32031] New: Sidebars and Breadcrumbs
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '26

21 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32031 Bug ID: 32031 Summary: Sidebars and Breadcrumbs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com With the staff client refresh I've had a nagging feeling about the breadcrumbs appearing above the sidebar navs.. it feels a bit messy but I hadn't come up with a better solution. I wonder about shifting the sidebar so it goes all the way to just under the top header and shift the breadcrumbs to the right... a bit like gitlab? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 32776] New: Choose to convert oldest reserve or all possible reserves to recalls
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '26

21 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32776 Bug ID: 32776 Summary: Choose to convert oldest reserve or all possible reserves to recalls 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 31415 introduces a script to convert reserves to recalls. By default, it will take the oldest reserve on a record and convert it to a recall. We should be able to customise which reserve(s) are converted to recalls. Options may include: - oldest reserve - one reserve for each issued item available to be recalled -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 34027] New: Add functionality to cleanup_database.pl to purge action logs in batches
by bugzilla-daemon＠bugs.koha-community.org 18 Sep '26

18 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34027 Bug ID: 34027 Summary: Add functionality to cleanup_database.pl to purge action logs in batches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Some of our libraries did not have the --logs argument in place for cleanup_database.pl and their action logs tables have grown very large (millions of rows) and taking up lots of space on the disk. We need to be able to clear these logs incrementally (in batches), as the sheer size of the delete query has overloaded the server. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 16994] New: Import and export MARC modification templates
by bugzilla-daemon＠bugs.koha-community.org 17 Sep '26

17 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16994 Bug ID: 16994 Summary: Import and export MARC modification templates Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Configuring a complicated MARC modification template can be a tedious job, so it would be nice to be able to import and export them the way we can with MARC frameworks. This would also facilitate sharing between libraries. -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 34069] New: Add ability to restore a recently deleted borrower from deletedborrowers
by bugzilla-daemon＠bugs.koha-community.org 17 Sep '26

17 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34069 Bug ID: 34069 Summary: Add ability to restore a recently deleted borrower from deletedborrowers 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: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be awesome to have the ability to restore a deleted borrower from deletedborrowers. Of course, if the borrower you need has been purged from that table for whatever reason, it wouldn't work, but it feels like an essential missing feature since we keep the data for Reasons anyway. Liz -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 137

[Bug 24194] New: Add system preference to hide expiration date options for reserves
by bugzilla-daemon＠bugs.koha-community.org 17 Sep '26

17 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24194 Bug ID: 24194 Summary: Add system preference to hide expiration date options for reserves 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: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Some libraries do not need to set expiration dates for reserves (this functionality is used). Add the ability to hide these options when placing reserves in staff client and OPAC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 162

[Bug 31028] New: Enhance 'Report a problem' to specify catalogue problems
by bugzilla-daemon＠bugs.koha-community.org 17 Sep '26

17 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31028 Bug ID: 31028 Summary: Enhance 'Report a problem' to specify catalogue problems Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Currently we have a generic 'Report a problem' link at the bottom of all pages on the OPAC.. however there's no easy way to report a problem about a specific biblio. We could add a more specific 'Report a problem with this record' option on the details display and record the biblionumber so staff can quickly see the record in context. -- You are receiving this mail because: You are watching all bug changes.

1 586

[Bug 40135] New: Record diff in action logs when modifying a biblio
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '26

16 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40135 Bug ID: 40135 Summary: Record diff in action logs when modifying a biblio 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 37940 Bibliographic record edits do not yet include a diff in the logs. They should. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37940 [Bug 37940] [OMNIBUS] All modification logged via action logs should include original to create JSON diff -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 48

[Bug 31484] New: Renewals disabled message doesn't display all reasons why something cannot be renewed
by bugzilla-daemon＠bugs.koha-community.org 16 Sep '26

16 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31484 Bug ID: 31484 Summary: Renewals disabled message doesn't display all reasons why something cannot be renewed 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There are many reasons why the renewals-disabled button might display in the issues table but not all of them will display depending on the circumstance, this can hamper librarians ability to make correct choices. For example: 1. Have an item checkout out what can be renewed at least one time BUT make that item overdue. 2. In the renewal column you'll see "0 Not allowed: overdue". That is good. 3. Have 'AllowRenewalOnHoldOverride' set to 'Don't allow' 4. Place the same item from 1-2 on hold. Make it an item level hold on that specific item. 5. Look at the issues table again, it still says "0 Not allowed: overdue". 6. The message should include some language saying the item can't be renewed becuase it is on hold AND it is overdue. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3