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

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

02 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 02 Apr '26

02 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

[Bug 32196] New: One should be able to remove a borrower relationship whenever one exists
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '26

02 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32196 Bug ID: 32196 Summary: One should be able to remove a borrower relationship whenever one exists Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 12446 Per bug 32195, there is still at least one way for a patron to end up with a guarantor in a category that does not allow guarantors. When that happens, the patron edit screen does not show one the relationship and therefore the relationship cannot be removed. One should *always* be able to remove an existing relationship. To recreate: 1: have a patron category where CanBeGuarantee is set to Yes. 2: Create a patron in that category, give them a guarantor 3: edit the patron category to set CanBeGuarantee to No 4: confirm your patron still has a guarantor that shows on the details page, but the guarantor no longer shows on the edit screen 5: this means the guarantor cannot be removed :( Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12446 [Bug 12446] Enable an adult to have a guarantor -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 40188] New: SUSHI has been renamed to COUNTER API
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '26

02 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40188 Bug ID: 40188 Summary: SUSHI has been renamed to COUNTER API Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: clemens.tubach(a)kit.edu, jonathan.druart(a)gmail.com, jonathan.field(a)openfifth.co.uk, martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, michaela.sieber(a)kit.edu, pedro.amorim(a)openfifth.co.uk Depends on: 39345 With the latest release of the COUNTER standard the protocol has been renamed from SUSHI to COUNTER API. https://www.countermetrics.org/wp-content/uploads/2024/04/Printable-Changes… At some point we might want to reflect that in the GUI as well. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39345 [Bug 39345] Koha must support COUNTER 5.1 -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 38822] New: View easilty the months for which usage reports have been collected for a given source
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '26

02 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38822 Bug ID: 38822 Summary: View easilty the months for which usage reports have been collected for a given source Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement 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 It could be nice to make it easy to view the months for which various usage reports have been collected for a given source (without the need to create a report in Koha) (FOLIO ERM or Coral could be source of inspiration) -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 37808] New: api.koha-community.org should be linked to from the main manual
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '26

02 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37808 Bug ID: 37808 Summary: api.koha-community.org should be linked to from the main manual Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: aude.charillon(a)ptfs-europe.com, philip.orr(a)lmscloud.de We currently don't highlight that there are publically available API docs available from the main documentation site: https://koha-community.org/manual/latest/en/html/webservices.html#versioned… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31557] New: Hold queue/home vs. holding library/transport cost matrix complications
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '26

02 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31557 Bug ID: 31557 Summary: Hold queue/home vs. holding library/transport cost matrix complications Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com It would be helpful if build_holds_queue.pl either 1) checked items' holding libraries in addition to home when items float, or 2) used the Transport Cost Matrix instead when systems have it enabled. Using home library only/first results in higher 'costs' and in holds being filled more slowly than necessary, and can be confusing for libraries. Home/holding: If I understand correctly, build_holds_queue.pl looks for items whose home library matches the hold's pickup library (plus accounting for any preferences set in StaticHoldsQueueWeight/HoldsQueueSkipClosed/RandomizeHoldsQueueWeight). For example, in a system where items float, a hold to be picked up at West library has the following items: Item 1: Home library West, holding library East Item 2: Home library West, holding library West Item 3: Home library North, holding library West If build_holds_queue.pl sees Item 1 first, it will be placed on East's queue to send to West even though Item 2 is already at West and could fill the hold more efficiently. Then since the Transport Cost Matrix is only consulted if no available items have a home library matching the hold's pickup library, holds are filled in a more 'expensive' way than libraries may expect. Using the Transport Cost Matrix directly would address this. For example, in a system where items float and a hold is to be picked up at South: Item 1: Home library East, holding library South Item 2: Home library West, holding library West Item 3: Home library South, holding library West build_holds_queue.pl will see that Item 3 has a home library matching the pickup library and will place it on West's queue to send to South. If build_holds_queue.pl consulted the Transport Cost Matrix, Item 1 would be placed on South's queue with no transfer necessary. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 37221] New: No way to turn off Overdrive integrations without removing all syspref values
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '26

02 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37221 Bug ID: 37221 Summary: No way to turn off Overdrive integrations without removing all syspref values Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org If the Overdrive API goes down, having this integration on at a busy site can cause backlogs due to timeouts that can only be mitigated by disabling the integration. As it stands to disable the integrations, you have to remove all of the values from the Overdrive preferences. It would be nice to be able to turn this integration on and off with a single syspref, retaining any previously supplied values for the overdrive integration. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 37181] New: Add --confirm option switch to pseudonymize_statistics.pl
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '26

02 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37181 Bug ID: 37181 Summary: Add --confirm option switch to pseudonymize_statistics.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 39127] New: When a table is wider than the page, the slider should move the table and not the whole page
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '26

02 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39127 Bug ID: 39127 Summary: When a table is wider than the page, the slider should move the table and not the whole page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When a table is wider than the page, a lateral slider is displayed at the bottom of the page. This slider should be displayed just under the table, and move only the table and not the whole page. It would be an UX impovement : viewing a large table shouldn't break the whole design of the page and make the side menu on the left of the page invisible. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22