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

[Bug 29908] New: Warning when empty ClaimReturnedWarningThreshold in patron_messages.inc
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29908 Bug ID: 29908 Summary: Warning when empty ClaimReturnedWarningThreshold in patron_messages.inc Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com System preference ClaimReturnedWarningThreshold manages the display of a patron message in case of too many claims. But this preference may be empty. This generates a warning : Argument "" isn't numeric in numeric gt (>) at /kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/en/includes/patron_messages.inc line 128. Default value should be considered has 0 or infinite ? Before Bug 27873 code was in templates, bug still applies. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 40720] New: Misleading tooltip text "remove all items" in Select2 fields
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40720 Bug ID: 40720 Summary: Misleading tooltip text "remove all items" in Select2 fields Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: elina.uotila(a)jarvenpaa.fi QA Contact: testopia(a)bugs.koha-community.org When editing an item record (for example, changing its current not for loan value) and hovering the cursor over the x symbol at the end of the field, Koha displays the tooltip text "remove all items". This wording is misleading, as the function does not remove any items from the database. Instead, it clears the selected value(s) in the drop-down menu. The affected text string comes from the messages-js.po file and is used by Select2 (koha-tmpl/intranet-tmpl/prog/js/select2.js:26). The fields where this text is used are all drop-down menus that are not directly related to items, so the wording "items" is confusing in this context. Would it be possible to change the phrase "remove all items" in Select2 to something more accurate, such as "remove selection"? -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 41082] New: Renaming columns in reports doesn't work with batch tools
by bugzilla-daemon＠bugs.koha-community.org 21 May '26

21 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41082 Bug ID: 41082 Summary: Renaming columns in reports doesn't work with batch tools Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com This is a bit of a curious case: When creating an SQL report and it contains the column itemnumber, we activate batch operations above the table. The itemnumber column can be renamed, using the syntax [[itemnumber|Exemplarnummer]], which gives us the option to translate the column name into something nicer for display. But: if you then send to batch item edit, the items are not transmitted. To test: 1) Create a report: select itemnumber, itemcallnumber from items; 2) Send some items to batch item edit, verify the items are shown above the item form 3) Update the report: select [[itemnumber|Exemplarnummer]], itemcallnumber from items; 4) Verify the report still shows as before with the batch options available and only the column being renamed. 5) Send some items to the batch item edit again, verify the items are NOT shown abvoe the item form => nothing would be batch edited. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 19

[Bug 42658] New: Add option for direct DB matching when using bulkmarcimport
by bugzilla-daemon＠bugs.koha-community.org 20 May '26

20 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42658 Bug ID: 42658 Summary: Add option for direct DB matching when using bulkmarcimport Initiative type: --- Sponsorship --- status: 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: jake.deery(a)openfifth.co.uk, robin(a)catalyst.net.nz Currently bulkmarcimport lets you define a matching rule when importing - often we are matching on the biblionumber/999c - this means searching ES or the DB is functionally equivalent. We should have an option to bypass the search engine and check the DB in these cases -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 42657] New: Improve bulkmarcimport
by bugzilla-daemon＠bugs.koha-community.org 20 May '26

20 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42657 Bug ID: 42657 Summary: Improve bulkmarcimport Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: jake.deery(a)openfifth.co.uk, robin(a)catalyst.net.nz Importing large numbers of records can be slow - opening this while investigating some improvements -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 42119] New: Update various admin pages to use grid layout for forms - Part 3
by bugzilla-daemon＠bugs.koha-community.org 20 May '26

20 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42119 Bug ID: 42119 Summary: Update various admin pages to use grid layout for forms - Part 3 Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Depends on: 41823 - Administration -> Curbside pickups - Administration -> Share content with Mana KB - Administration -> Z39.50 servers Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41823 [Bug 41823] Update acquisitions admin pages to use grid layout for forms -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 8127] Most-circulated items report doesn't work when limited by library
by bugzilla-daemon＠bugs.koha-community.org 20 May '26

20 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127 --- Comment #7 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Comment 4 contains a typo, remove the S> before executing -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8127] Most-circulated items report doesn't work when limited by library
by bugzilla-daemon＠bugs.koha-community.org 20 May '26

20 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127 --- Comment #6 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Created attachment 199342 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=199342&action=e… Bug 8127: Fix filters use in 'Most-circulated items report' Filters are broken for many reasons. Previous patch contains some (little) tidying. There are 3 parts in this patch: 1 - The column name is incorrectly named in the dropdown for "branch", it is added in this patch 2 - There is a definition for 'Day' and 'Month', but not for 'Week', it is also added in this patch 3 - Dbh variables are passed in the string definition AND in the call. I removed them from the string definition since it violates the coding guidelines. Test plan: 1. On an fresh ktd db, run the script provided here (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127#c3) to fill the database with checkins/checkouts: Visit http://your_koha:8081/cgi-bin/koha/reports/cat_issues_top.pl 2. Run a baseline test with following params: Checkout date from 01/01/2020 Checkout date to: tomorrow Library: Any library Fill nothing else Notice it is works 3. Test with some limits (Library, Week, and any other), notice you encounter errors on Library and Week, and that any other is empty, without error. 4. Apply patch 5. Rerun 2-3 and notice you now have results. Check with each possible limit, limiting to 5. Test once with 10 as a limit. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8127] Most-circulated items report doesn't work when limited by library
by bugzilla-daemon＠bugs.koha-community.org 20 May '26

20 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127 --- Comment #5 from Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> --- Created attachment 199341 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=199341&action=e… Bug 8127: Remove useless commented warns Patch from commit f821cb6 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8127] Most-circulated items report doesn't work when limited by library
by bugzilla-daemon＠bugs.koha-community.org 20 May '26

20 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8127 Baptiste Wojtkowski (bwoj) <baptiste.wojtkowski(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Patch complexity|--- |Small patch Status|ASSIGNED |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0