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

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 --- Comment #28 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- I feel like I am just speaking into the air here. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 38296] New: Investigate DataTables's extension StateRestore
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38296 Bug ID: 38296 Summary: Investigate DataTables's extension StateRestore Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement 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: 33484, 36640 https://datatables.net/extensions/staterestore/index#Features Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33484 [Bug 33484] Ability to remember user's selected table configuration and search filters for tables https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36640 [Bug 36640] Upgrade DataTables from 1.13.6 to 2.x -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 31159] New: Can we drop the 'CircSideBar' preference and convert the sidebar to being collapsible?
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31159 Bug ID: 31159 Summary: Can we drop the 'CircSideBar' preference and convert the sidebar to being collapsible? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I find it confusing that the CircSidebar is disabled by default. I propose we enable it and remove the preference replacing it with a collapsible navigation that gives us the best of both worlds. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 41747] New: xt/js_tidy is failing on ill js files
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41747 Bug ID: 41747 Summary: xt/js_tidy is failing on ill js files Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org 20:04:28 koha-1 | # Failed test 'koha-tmpl/intranet-tmpl/prog/js/ill-availability.js should be kept tidy' 20:04:28 koha-1 | # at xt/js_tidy.t line 36. 20:04:28 koha-1 | 20:04:28 koha-1 | # Failed test 'koha-tmpl/opac-tmpl/bootstrap/js/ill-availability.js should be kept tidy' 20:04:28 koha-1 | # at xt/js_tidy.t line 36. 20:04:28 koha-1 | Everything up-to-date 20:04:28 koha-1 | # Looks like you failed 2 tests of 3. 20:04:28 koha-1 | [20:03:48] xt/js_tidy.t ................................................................ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 42272] New: Purchase Suggestion search by bibliographic information broken
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42272 Bug ID: 42272 Summary: Purchase Suggestion search by bibliographic information broken Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: Create a suggestion with a title "Calico Captive" with a branch that matches your branch. Go to the suggestion page and use the left hand side "Bibliographic Information" search to search for your title. No results are returned, even if there is one that should be. With copyright date it also throws a datatable error. The title can still be filtered in the table filter. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 42018] New: Inconsistent behavior for null values for fields selected in PatronDuplicateMatchingAddFields
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42018 Bug ID: 42018 Summary: Inconsistent behavior for null values for fields selected in PatronDuplicateMatchingAddFields Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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(a)bywatersolutions.com PatronDuplicateMatchingAddFields behaves differently for null values depending on whether the null values are in the existing patron record or the record being created. To replicate: -Set PatronDuplicateMatchingAddFields to surname, firstname, email Scenario 1: -Create patron A with a first name and surname, but null email -Create patron B with a first name and surname matching patron A, but a value in email -----> NOT FLAGGED as duplicate Scenario 2: -Create patron A with a first name, surname, and email -Create patron B with a first name and surname matching patron A, but null email -----> FLAGGED as duplicate It seems that the two scenarios should behave the same way, or that there should be documentation of the different behavior in the manual. This applies to 40082 but is also true for duplicate matching in the staff interface. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 42326] New: Link back to label batch after exporting
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42326 Bug ID: 42326 Summary: Link back to label batch after exporting Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: emily.lamancusa(a)montgomerycountymd.gov Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Depends on: 40366 When staff export a label batch for printing, they often want to delete the batch after verifying that it exported correctly. Currently, the export page only links back to the full list of label batches, so staff need to find the same batch again if they want to delete it, remove items, etc. It would be really helpful to include a link directly back to the label batch from the export page. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40366 [Bug 40366] Update the label export process to avoid Greybox modal -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 40366] New: Update the label export process to avoid Greybox modal
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40366 Bug ID: 40366 Summary: Update the label export process to avoid Greybox modal Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Label/patron card printing Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org I propose that we update the label export process in order to avoid using a Greybox modal. We can just as easily move from page to page as the process progresses. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 41425] New: Log entries for merging patrons are untranslatable
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41425 Bug ID: 41425 Summary: Log entries for merging patrons are untranslatable Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: f.demians(a)tamil.fr, jonathan.druart(a)gmail.com Depends on: 22632 Koha/Patron.pm: . " has been merged into " We should never hardcode strings into .pm, they are not translatable. This should be solved on template level instead. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22632 [Bug 22632] Add logging of merged patrons -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 27357] New: Trigger printing of a routing list, when an issue is received
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27357 Bug ID: 27357 Summary: Trigger printing of a routing list, when an issue is received Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment the printing of a routing list happens separately from receiving the issue and requires extra steps and attention to not be forgotten. It would be nice, if the printing of a routing list was triggered by receiving an issue to have a more streamlined process. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1