May 2026 - Koha-bugs - lists.koha-community.org

[Bug 41964] New: Upgrade the Multiple Select plugin in the staff interface to 2.3.1
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41964 Bug ID: 41964 Summary: Upgrade the Multiple Select plugin in the staff interface to 2.3.1 Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org We last upgraded the Multiple Select plugin (https://github.com/wenzhixin/multiple-select) with Bug 33868 in 2023. We can now upgrade from 1.6.0 to the current 2.3.1. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 40255] New: Allow custom debit descriptions
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40255 Bug ID: 40255 Summary: Allow custom debit descriptions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 24865 made it possible to use a notice to replace the default wording of the description for overdue fines. It would be helpful to expand that functionality to all debit types, both system-defined and local. It might make more sense to put this within the Debit Type setup than to continue using notices, though. These custom descriptions would allow Template Toolkit as notices do, however, for formatting, logic, and value transformation -- for example, one library wants the description to tell what portion of the fee goes to local tax. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 73

[Bug 42085] New: Permissions should be logged when a patron is deleted
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42085 Bug ID: 42085 Summary: Permissions should be logged when a patron is deleted Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a patron is deleted, patrons permission's are not logged. This would be helpful for auditing purposes (ex-employee account was decomissioned, had X permissions at the time) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 41994] New: REST API route to list system preferences
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41994 Bug ID: 41994 Summary: REST API route to list system preferences Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 39158] New: Reduce code duplication in marc_records_to_documents
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39158 Bug ID: 39158 Summary: Reduce code duplication in marc_records_to_documents Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org There is currently a block in Koha::SearchEngine::Elasticsearch::marc_records_to_documents that in my opinion should be brokwn out to its own method for increased maintainability and readability. It's easily done that these two blocks will drift apart with time (when they should be the same), fixing a bug in one place, forgetting in another etc. Here is a patch to fix this. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 41638] New: Patron record field labels lack distinct id in HTML
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41638 Bug ID: 41638 Summary: Patron record field labels lack distinct id in HTML Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Libraries commonly use jQuery to reword the labels on various fields in the patron record (like changing "Surname" to "Last name"). Those field labels lack distinct IDs, which makes targeting them with jQuery more complicated and fragile: $('.label:contains("Surname")').text('Last name:'); $('label[for="surname"]').text("Last name:"); If that label had an ID like "#surname_label" it would simplify things. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 40841] New: Limit z39.50 targets to specific branches
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40841 Bug ID: 40841 Summary: Limit z39.50 targets to specific branches Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement 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 Within larger systems, catalogers at each individual library have different z39.50 targets that they prefer to use or are allowed access to. It would be good to limit z39.50 targets based on the user's logged-in branch. Bug 5316 proposes limiting access per user. While that could also be helpful, limiting by branch offers a more lightweight and flexible option. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 85

[Bug 40853] New: ElasticsearchBoostFieldMatch - needs to boost results more
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40853 Bug ID: 40853 Summary: ElasticsearchBoostFieldMatch - needs to boost results more Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When searching for book titles that may have words in many fields, e.g. 'book of hope', the boost is not enough, especially when other fields like 'title' are boosted. In production with title boost of 32 the general results are getting a score of ~600 The boost query is getting a score of ~10 - not enough to boost past the general results We can try a few things: 1 - Use the 'boost' field from 'title-cover' matching in the extra query 2 - Add a system preference (or hard code) to define how much to boost the additional query by 3 - Try using a boost query rather than a bool query: https://www.elastic.co/docs/reference/query-languages/query-dsl/query-dsl-b… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 41814] New: Limit the maximum age for borrower categories without a specified range
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41814 Bug ID: 41814 Summary: Limit the maximum age for borrower categories without a specified range Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: jake.deery(a)openfifth.co.uk Reporter: jake.deery(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com We should be able to optionally set a maximum age for any borrower categories that don't already have a specified range. This is already possible on the OPAC with PatronSelfRegistrationAgeRange, I propose a PatronAgeRange that applies to the intranet, as well as the OPAC (if PatronSelfRegistrationAgeRange is not set). -- You are receiving this mail because: You are watching all bug changes.

1 23

[Bug 41107] New: Create an API endpoint to get Koha version
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41107 Bug ID: 41107 Summary: Create an API endpoint to get Koha version Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com It would be helpful to have an API endpoint from which to get the Koha version of a system -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21