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

[Bug 40551] New: Make patron page holds table use API endpoint for cancellation
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '26

03 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40551 Bug ID: 40551 Summary: Make patron page holds table use API endpoint for cancellation 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: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 38115] New: Add FTP support to export_records.pl
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '26

03 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38115 Bug ID: 38115 Summary: Add FTP support to export_records.pl Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz With an administrative UI for configuring FTP connections coming but bug 35761 it would be nice to add support for using those connections in the misc/export_records.pl script. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 39

[Bug 39972] New: Blank bib heading fields link to unrelated authority records
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '26

03 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39972 Bug ID: 39972 Summary: Blank bib heading fields link to unrelated authority records Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: maxeinergl(a)gcc.edu QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you save a bib record with a heading field (1xx, 6xx, etc.) containing a blank subfield a or other subfields but no subfield a, Koha incorrectly links the field to an authority record. It's not a blank authority, but a proper authority record of the same type (personal, topical etc.) but a nonmatching heading. It seems to target the same records each time, so in my system a blank personal name field (100, 600, etc.) always links to authority ID #1, for the Achaemenid dynasty. A blank X10 links to authority #48, for the Catholic Church, and so on. The situations described are cataloging errors in the bib record and so unwelcome, but they should not automatically link to valid but unrelated authorities. They should remain unlinked. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 42055] New: Real time holds queue doesn't rebuild when hold from group hold is filled
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '26

03 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42055 Bug ID: 42055 Summary: Real time holds queue doesn't rebuild when hold from group hold is filled Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com If a library is using the real-time holds queue and a hold that is part of a group hold/hyperhold is filled, the queue isn't rebuilt to remove the other titles. To replicate: -Make sure library is using the real-time holds queue. -Create a group hold with multiple items available at one or more libraries. -Note that all available titles show on the holds queue(s) (see bug 42054). -Check an item in to satisfy the hold group. -Re-run the holds queue(s), and note that the other items from the group hold still show. The queue only appears to rebuild once the item that filled the hold is checked out. If a library checks one of the other items from the group in after the hold has been filled, the later item(s) won't trigger. This is correct behavior, but the fact that the other titles from the group still show on the queue is likely to cause significant frustration and confusion for libraries. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 41840] New: Number in patron's Holds tab doesn't update for new groups until page is reloaded
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '26

03 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41840 Bug ID: 41840 Summary: Number in patron's Holds tab doesn't update for new groups until page is reloaded Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com With the new hold groups feature, the number next to the Holds label in a patron's Holds table (staff interface view) lists the combined number of groups and individual holds. For instance, if a patron has one group hold with two bibs, and then two individual holds, the number next to Holds will read 3. However, if a staff member creates a new group from that screen by adding one of the ungrouped holds to the existing group, the number next to the Holds label will still show as 3 until the page is reloaded. Once it's reloaded, the number will correctly update to 2 (one group with three bibs, and one individual hold). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 42184] New: Transfer requests between the ILL module and purchase suggestsions
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '26

03 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42184 Bug ID: 42184 Summary: Transfer requests between the ILL module and purchase suggestsions Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com It would be extremely helpful if there were a way to move an ILL request to purchase suggestions, or vice versa. Some things we might want to purchase, and some we only want to borrow. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31520] New: Only log ILL changes that are actual changes
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '26

03 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31520 Bug ID: 31520 Summary: Only log ILL changes that are actual changes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no "Bug 20750 - Allow timestamped auditing of ILL request events" added the ability to log status changes to ILL requests, in the action_logs table, with action = 'STATUS_CHANGE'. I have an ILL setup where a remote API is checked for data every 3 minutes, and requests are updated. With Illlog = on, this leads to 480 action_logs entries per 24-hour period. I have a test setup where the amount of logs was causing the detailed display of illrequests to time out, because there were so many log entries to fetch. This could be improved if we only logged actual status changes. Today there is a log entry even if the status is not changed: | ILL | STATUS_CHANGE | {"status_after":"IN_LEV","log_origin":"core","status_before":"IN_LEV"} | | ILL | STATUS_CHANGE | {"status_after":"IN_LEV","status_before":"IN_LEV","log_origin":"core"} | | ILL | STATUS_CHANGE | {"status_before":"IN_LEV","status_after":"IN_LEV","log_origin":"core"} | | ILL | STATUS_CHANGE | {"log_origin":"core","status_before":"IN_LEV","status_after":"IN_LEV"} | | ILL | STATUS_CHANGE | {"status_before":"IN_LEV","status_after":"IN_LEV","log_origin":"core"} | | ILL | STATUS_CHANGE | {"status_after":"IN_LEV","log_origin":"core","status_before":"IN_LEV"} | +--------+---------------+------------------------------------------------------------------------+ We could compare status_before and status_after, and only log if they differ. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 32896] New: Can we move autoBarcode handling into Koha::Item->store() ?
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '26

03 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32896 Bug ID: 32896 Summary: Can we move autoBarcode handling into Koha::Item->store() ? Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Currently, the codebase is somewhat littered with calls to check the autoBarcode pref and then generate a barcode.. could we remove these calls from the various controllers and move it to one call in Koha::Item->store() instead? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 31380] New: Build Mojolicious controller for running Koha plugins
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '26

03 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31380 Bug ID: 31380 Summary: Build Mojolicious controller for running Koha plugins Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org At the moment, Koha plugins run via Plack::App::CGIBin, which buffers responses and otherwise prevents plugins from fully leveraging the power of Plack and Mojolicious. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 81

[Bug 33768] New: We need tests for the OAuth2/OIDC client
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '26

03 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33768 Bug ID: 33768 Summary: We need tests for the OAuth2/OIDC client 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 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4