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

[Bug 39932] New: Koha::Item->_status should return an array
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39932 Bug ID: 39932 Summary: Koha::Item->_status should return an array Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com The `_status` method has a couple problems: * It doesn't have a POD * It returns a string! It should return a list instead, so handling on the UI doesn't require splitting the string back. That said, the tests using it in the UI (Holdings_spec.ts) only test the `available` rendering use case. This is minor. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 39000] New: "Encoding errors" block on detail page hurt the eyes
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39000 Bug ID: 39000 Summary: "Encoding errors" block on detail page hurt the eyes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 35402 https://snipboard.io/wUmV50.jpg Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35402 [Bug 35402] Update the OPAC and staff interface to Bootstrap 5 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22

[Bug 39346] New: Only 20 supplementary fields are usable in Agreements
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39346 Bug ID: 39346 Summary: Only 20 supplementary fields are usable in Agreements Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(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 In administration, create 25 supplementary fields for ERM Agreements In ERM module, create an agreement : only 20 of the supplementary fields will be displayed It must be an issue with API call? Maybe it affects also other parts of Koha? If so it should be fixed everywhere -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 39180] New: Handle and report exception at checkout/checkin due to missing guarantor
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39180 Bug ID: 39180 Summary: Handle and report exception at checkout/checkin due to missing guarantor Change sponsored?: --- Product: Koha Version: Main 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 When ChildNeedsGuarantor is enabled, Koha will throw an exception and fail to check an item in if the borrowing patron could have a guarantor but does not. The failed checkin gives a generic messages about configuration issues. We should check the item in and report on the screen that the patron should have a guarantor. To recreate: 1 - have a patron in a category that can be a guarantee but does not have a guarantor on their account 2 - set TrackLastPatronActivityTriggers to update the patron on checkin of an item 3 - check an item out to your patron 4 - set ChildNeedsGuarantor to "must have" 5 - check your item in, get error It also throws an exception at checkout if your tell TrackLastPatronActivityTriggers to update at checkout, but the checkout succeeds. We've seen inconsistent behavior between production and test sites around the specifics of this error that we haven't quite nailed down yet. It's possible something changed here between 24.05.06 and main as they generate this error slightly differently. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 35826] New: Optimize building of holds queue based on transport cost matrix
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35826 Bug ID: 35826 Summary: Optimize building of holds queue based on transport cost matrix 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: andreas.jonsson(a)kreablo.se QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com There are several problems when building the holds queue which makes it hard for the libraries to predict the outcome for how items are allocated based on their configured policy. 1. The allocation of items should be done by optimizing on transport cost. Currently a greedy algorithm is applied when building the holds queue which doesn't always produce optimal results. 2. The allocation of items should not fall back to some default allocation if an allocation by using the transport cost matrix fails. If no allocation can be found that satisfies the configured constraints it is a violation of the configured policies o proceed and make an allocation. 3. Although items at the local library have transport cost 0, assigning local items should not be given absolute precedence. It is simply false that assigning local items "is obviously the least costly" as the comment says. (That we hard code the cost to 0 for local items is also an arbitrary restriction in Koha, there is no technical reason as to why we shouldn't allow the libraries to set a cost for allocating local items.) I am currently working on a solution based on the Hungarian Algorithm. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 75

[Bug 17437] New: Advanced cataloging editor - editing the 001 field overwrites data
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17437 Bug ID: 17437 Summary: Advanced cataloging editor - editing the 001 field overwrites data Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the Advanced Cataloging Editor, when you add any data to the beginning of the 001 tag it types over the data already entered in the field. For example, adding the 'ocn' prefix to OCLC numbers in the advanced editor overwrites the first 3 digits of the OCLC number, causing you to reenter the data. In the basic editor you can enter data in the 001 without it overwriting an current data in the field. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 23674] New: Allowing editable notes when posting Payments/Writeoffs
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23674 Bug ID: 23674 Summary: Allowing editable notes when posting Payments/Writeoffs Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice if a librarian forgot to add a note to a payment/write-off/manual invoice transaction, or if a note was added at time of transaction, that this note is editable. Currently, this is not something that can be edited, therefore, a librarian would have to remove the entire transaction to edit the note. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 109

[Bug 39662] New: Register a new account page - X next to calendar is confusing, should say "Clear"
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39662 Bug ID: 39662 Summary: Register a new account page - X next to calendar is confusing, should say "Clear" Change sponsored?: --- Product: Koha Version: Main Hardware: All URL: http://localhost:8080/cgi-bin/koha/opac-memberentry.pl OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: kristinamason(a)fastmail.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org Created attachment 181050 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=181050&action=e… Form screenshot To reproduce: load http://localhost:8080/cgi-bin/koha/opac-memberentry.pl Issue: On the "Register a new account" page, next to the calendar there is a red X. To a new user, like me, it looks like an error message. I had to ask to receive clarification that it actually clears the field. It would be more clear to the user if the X were styled differently to look like a button, and not red like an error. This issue might be present on other forms. I've attached an example of a button style that might be more user friendly. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 31481] New: Pass message_id to SMS drivers
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31481 Bug ID: 31481 Summary: Pass message_id to SMS drivers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Most of the SMS Gateways support REST API and it is common that the operator sends their report back to the service. Now it is impossible to catch reports if sms was succesfully sent or it failed since we can't pass the message_id to our report url when sending the message to the gateway. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 16188] New: SMS via email not applicable in India due to telecom regulation
by bugzilla-daemon＠bugs.koha-community.org 28 Feb '26

28 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16188 Bug ID: 16188 Summary: SMS via email not applicable in India due to telecom regulation Change sponsored?: --- Product: Koha Version: master Hardware: All URL: https://lists.katipo.co.nz/pipermail/koha/2016-April/0 45114.html OS: All Status: ASSIGNED Severity: minor Priority: P5 - low Component: Notices Assignee: indradg(a)gmail.com Reporter: indradg(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 9021 Due to the nature of telecom regulatory framework in India, bug 9021 will not work for 99% of 500+ million cell phones in India. Details as explained in this mail with specific examples - https://lists.katipo.co.nz/pipermail/koha/2016-April/045114.html This patch adds a "note" for such exceptions like India in the provider setup screen. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9021 [Bug 9021] Add SMS via email as an alternative to SMS services via SMS::Send drivers -- You are receiving this mail because: You are watching all bug changes.

1 17