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

[Bug 37711] New: IdP auto-register should work on the staff interface
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '26

20 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37711 Bug ID: 37711 Summary: IdP auto-register should work on the staff interface Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Right now it only works if the login happens in the OPAC. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 87

[Bug 28318] New: accounlintes.credit_number missing on the API
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '26

20 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28318 Bug ID: 28318 Summary: accounlintes.credit_number missing on the API Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com It was added to the DB structure, but bug 28272 skipped it so we could ponder if it is required on the API object and how should we name it. Feels like 'credit_sequence_number' could be a good name for it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 28964] New: request.pl slow to load when there are many holds on a record
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '26

20 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28964 Bug ID: 28964 Summary: request.pl slow to load when there are many holds on a record Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In a large consortium popular titles have many holds - a record with 700 holds takes about 24 seconds to load When trying to place a hold we shouldn't have to wait for all holds to load. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 29124] New: Load existing holds requests using API
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '26

20 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29124 Bug ID: 29124 Summary: Load existing holds requests using API 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We generate a lot of data when a record has many holds and we load the table of existing holds - we should load this dynamically after the page load using the API -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 27515] New: Search for both cases
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '26

20 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27515 Bug ID: 27515 Summary: Search for both cases Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org When searching for the book "The Sawdust Dream", if you search for "sawdust dream", you get the item in the results. When you search for "sawdust dreams", you get nothing. It would be great if Koha would check for singular iterations of words used. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 41899] New: Add branchcode in accountlines.branchcode for RESERVE_EXPIRED
by bugzilla-daemon＠bugs.koha-community.org 20 Feb '26

20 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41899 Bug ID: 41899 Summary: Add branchcode in accountlines.branchcode for RESERVE_EXPIRED Initiative type: --- Sponsorship --- status: 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: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org We need to record the branchcode to the accountlines when the RESERVE_EXPIRED fee is added by the cancel_expired_holds.pl cron job. I think the suitable branchcode could be the hold's pickup library (reserves.branchcode). This change would help to track to which library the fee belongs to (in library consortiums). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 2646] Add sort option for the series number
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '26

19 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2646 --- Comment #13 from Sarah Cornell <sbcornell(a)cityofportsmouth.com> --- We have a nasty assortment of series data as well, but perhaps that helps find all the edge cases! Currently Koha displays series statements in the 490 or 8XX based on the 490 ind1 data. (as of the last time we checked!) It would be good for Koha to use the same or at least consistent logic (.e.g. if 490$v exists, use 490$v, if 490$v does not exist, use 8XX$v) to sort based on series. Also, could a system preference tell Koha which series field to sort by? If a library wants to prefer 8XX$v regardless of the presence of 490$v, then they cantell their system exactly what field to consult when using a "sort by series number" option. Just some ideas. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 2646] Add sort option for the series number
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '26

19 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2646 --- Comment #12 from Esther Melander <esther.melander(a)bywatersolutions.com> --- How would Koha handle a series sort when there is more than one series statement with different volume numbers? I am thinking of the Magic Tree House series which was originally published with one series order and then the publisher re-did the series with a new order. That would mean a title could conceivably have two series statements and be sorted in two different ways. This may be an edge example, but I'm sure there are others. -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 2646] Add sort option for the series number
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '26

19 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2646 --- Comment #11 from Jason Robb <jrobb(a)sekls.org> --- We have a nice nasty mix of series data in 440s, 490s and 8XXs so we'd want to be able to consider all the possible series fields when doing the sort. Our series titles aren't at all consistent either. I wonder if this would be simplified by only sorting when the search is limited to a specific series title search? -- You are receiving this mail because: You are watching all bug changes. You are the QA Contact for the bug.

1 0

[Bug 2646] Add sort option for the series number
by bugzilla-daemon＠bugs.koha-community.org 19 Feb '26

19 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2646 Jason Robb <jrobb(a)sekls.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jrobb(a)sekls.org -- You are receiving this mail because: You are watching all bug changes.

1 0