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

[Bug 40478] New: Add option to center barcode on labels
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40478 Bug ID: 40478 Summary: Add option to center barcode on labels Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Bug 40473 fixes barcode length calculator of Code39 barcodes in the label creator. When using barcode width of 1 or 100%, the barcode will be centred on the label. But if you use a smaller barcode width, your barcode will be left aligned. Surely it would be good to have the ability to have centred barcodes even when using narrower barcodes? -- You are receiving this mail because: You are watching all bug changes.

1 22

[Bug 42588] New: biblio.uncancelled_orders+count is not sortable on the API
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42588 Bug ID: 42588 Summary: biblio.uncancelled_orders+count is not sortable on the API 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 41950 The biblio.uncancelled_orders+count embed on the acquisitions orders endpoint cannot be sorted because the uncancelled_orders DBIC relationship does not exist on the Biblio result class. The Koha::Biblio->uncancelled_orders method currently calls self->orders->filter_out_cancelled which filters on datecancellationprinted => undef in Perl. To make it sortable, we need: 1. A DBIC coderef relationship on Biblio that filters aqorders.datecancellationprinted IS NULL 2. Support for undef values (IS NULL) in _build_count_subquery 3. Update Koha::Biblio->uncancelled_orders to delegate to the DBIC relationship 4. Unit tests proving the sort works The generated subquery would be: (SELECT COUNT(*) FROM aqorders WHERE aqorders.biblionumber = me.biblionumber AND aqorders.datecancellationprinted IS NULL) Test plan: prove t/Koha/REST/Plugin/Query.t t/db_dependent/api/v1/acquisitions_orders.t t/db_dependent/Koha/Biblio.t Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41950 [Bug 41950] Make +count embeds sortable by using SQL-level COUNT subqueries -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 42591] New: current_item_level_holds+count is not sortable on the API
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42591 Bug ID: 42591 Summary: current_item_level_holds+count is not sortable on the API 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 41950 The current_item_level_holds+count embed on the acquisitions orders endpoint cannot be sorted because the underlying query is too complex for a single DBIC relationship. Koha::Acquisition::Order->current_item_level_holds requires: 1. Getting item numbers from aqorders_items for the order 2. Getting the biblio for the order 3. Querying holds on that biblio filtered by reservedate <= NOW() + ConfirmFutureHolds AND itemnumber IN (those items) This involves a syspref-dependent date calculation and a multi-table correlation that cannot be expressed as a DBIC relationship coderef. A possible approach would be a raw SQL subquery override mechanism in _build_count_subquery, or accepting that this embed remains display-only (not sortable). Test plan: prove t/db_dependent/api/v1/acquisitions_orders.t Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41950 [Bug 41950] Make +count embeds sortable by using SQL-level COUNT subqueries -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 42617] New: ILL availability pagination not working
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42617 Bug ID: 42617 Summary: ILL availability pagination not working Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 42592] New: Flag +count embeds that cannot be sorted
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42592 Bug ID: 42592 Summary: Flag +count embeds that cannot be sorted 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 41950 After bug 41950, +count embeds backed by a DBIC relationship are automatically sortable. However, some +count embeds are only computed at the Perl level (no matching DBIC relationship) and cannot be sorted. Currently, consumers discover this only by receiving a 400 error when attempting to sort. We need a mechanism to flag or advertise which +count embeds are sortable and which are not. This could be: 1. An annotation in the OpenAPI spec (e.g. x-sortable: false on the embed enum value) 2. A response header listing sortable fields 3. Documentation in the API markdown 4. A dedicated endpoint or metadata response The goal is to let API consumers know upfront which +count columns support sorting, without trial and error. Discussion started in bug 41950 comment 17. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41950 [Bug 41950] Make +count embeds sortable by using SQL-level COUNT subqueries -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 42587] New: overdues+count is not sortable on the API
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42587 Bug ID: 42587 Summary: overdues+count is not sortable on the API 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 41950 The overdues+count embed on the patrons endpoint cannot be sorted because the overdues DBIC relationship does not exist on the Borrower result class. The Koha::Patron->overdues method currently filters checkouts in Perl (date_due < NOW()). To make it sortable, we need: 1. A DBIC coderef relationship on Borrower that filters issues.date_due < NOW() at the SQL level 2. Teach _build_count_subquery to handle coderef conditions (invoke the coderef, parse the returned hashref into WHERE clauses) 3. Update Koha::Patron->overdues to delegate to the DBIC relationship 4. Unit tests proving the sort works with a mix of overdue and non-overdue checkouts The generated subquery would be: (SELECT COUNT(*) FROM issues WHERE issues.borrowernumber = me.borrowernumber AND issues.date_due < NOW()) Test plan: prove t/Koha/REST/Plugin/Query.t t/db_dependent/api/v1/patrons.t t/db_dependent/Koha/Patron.t Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41950 [Bug 41950] Make +count embeds sortable by using SQL-level COUNT subqueries -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 42519] New: Terminology: branch should be library
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42519 Bug ID: 42519 Summary: Terminology: branch should be library Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: Academy Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Found while translating main: koha-tmpl/intranet-tmpl/prog/en/modules/admin/categories.tt:578 Your self-renewal can't be processed at this time. Please visit your local branch to complete your renewal. Also: for installations with only one library this might sound little odd, maybe just: visit your library? -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 39726] New: Remove ConnectSuggestionAndBiblio from C4/Suggestions.pm
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39726 Bug ID: 39726 Summary: Remove ConnectSuggestionAndBiblio from C4/Suggestions.pm Change sponsored?: --- Product: Koha Version: Main 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: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23990 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 42589] New: bundle_items_lost+count is not sortable on the API
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42589 Bug ID: 42589 Summary: bundle_items_lost+count is not sortable on the API 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 41950 The bundle_items_lost+count embed on the biblio items endpoint cannot be sorted because the bundle_items_lost DBIC relationship does not exist on the Item result class. The Koha::Item->bundle_items_lost method currently uses a many_to_many accessor with a Perl-side filter (itemlost != 0). To make it sortable, we need: 1. A DBIC coderef relationship on Item pointing to Koha::Schema::Result::Item with an -in subquery through the item_bundles bridge table and a filter on itemlost != 0 2. Support for -in with scalar ref (literal SQL) in _build_count_subquery 3. Update Koha::Item->bundle_items_lost to delegate to the DBIC relationship 4. Unit tests proving the sort works The generated subquery would be: (SELECT COUNT(*) FROM items WHERE items.itemnumber IN (SELECT item FROM item_bundles WHERE host = me.itemnumber) AND items.itemlost != 0) Performance note: This uses a correlated IN subquery. For large catalogs with many bundles, this could be slow. An alternative would be a JOIN-based COUNT, but that requires more complex changes to _build_count_subquery. The trade-off should be evaluated. Test plan: prove t/Koha/REST/Plugin/Query.t t/db_dependent/api/v1/biblios.t t/db_dependent/Koha/Item.t Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41950 [Bug 41950] Make +count embeds sortable by using SQL-level COUNT subqueries -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 42590] New: bundle_items_not_lost+count is not sortable on the API
by bugzilla-daemon＠bugs.koha-community.org 12 Jul '26

12 Jul '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42590 Bug ID: 42590 Summary: bundle_items_not_lost+count is not sortable on the API 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Depends on: 41950 The bundle_items_not_lost+count embed on the biblio items endpoint cannot be sorted because the bundle_items_not_lost DBIC relationship does not exist on the Item result class. Same approach as bundle_items_lost+count (bug 42589) but filtering on itemlost = 0. The generated subquery would be: (SELECT COUNT(*) FROM items WHERE items.itemnumber IN (SELECT item FROM item_bundles WHERE host = me.itemnumber) AND items.itemlost = 0) Performance note: Same correlated IN subquery concern as bundle_items_lost+count. The trade-off should be evaluated. Test plan: prove t/Koha/REST/Plugin/Query.t t/db_dependent/api/v1/biblios.t t/db_dependent/Koha/Item.t Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41950 [Bug 41950] Make +count embeds sortable by using SQL-level COUNT subqueries -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2