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

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 --- Comment #618 from Nick Clemens (kidclamp) <nick(a)bywatersolutions.com> --- When visiting the page too, it would be nice to automatically limit to the current signed in library on the initial load -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 Nick Clemens (kidclamp) <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #617 from Nick Clemens (kidclamp) <nick(a)bywatersolutions.com> --- This is super cool - I imported a big libraries rules for testing, it worked well - the list is overwhelming at first, but once filters are used it works nicely. Things I found: When editing the triggers it would be nice to have the circulation rule displayed under the context, and the context itself should display as informational, not required form fields , it may confuse the user. The headers could be a little more verbose so librarians understand the circulation rules are being pulled form the context. We might want to see renewal/autorenewal information as well When editing a trigger the buttons to switch which trigger is being edited do not always work The dropdowns are in code order, they should be in description/name order If I run the overdue notices cron with --list-all I get notices for all categories, even if they don't match, even I select triggered Without list-all it works, this could be existing bug? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 Chloé Zermatten <chloe.zermatten(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 --- Comment #616 from Chloé Zermatten <chloe.zermatten(a)openfifth.co.uk> --- (In reply to Victor Grousset/tuxayo from comment #614) > Thanks for the updated patches. I got this error with tests: > > kohadev-koha@kohadevbox:koha(testing-SO-QA)$ prove > /kohadevbox/koha/t/Koha/Auth/Permissions.t > /kohadevbox/koha/t/Koha/Auth/Permissions.t .. 1/4 > # Failed test 'Expected permissions generated for superlibrarian' > # at /kohadevbox/koha/t/Koha/Auth/Permissions.t line 314. > # Structures begin differing at: > # $got->{CAN_user_parameters_manage_circ_triggers} = '1' > # $expected->{CAN_user_parameters_manage_circ_triggers} = Does not > exist > # Looks like you failed 1 test of 1. > > I don't think is a setup step that should be missing. I started KTD with the > patches already. And redoing the updatedatabase doesn't help. > > ----- > > QA script reports this: > [FAIL] koha-tmpl/intranet-tmpl/prog/js/vue/stores/circulation-rules.js > FAIL forbidden_patterns > forbidden pattern: Use __("") instead of _("") (line 371) > > It's just this: > https://wiki.koha-community.org/wiki/User:Victor_Grousset_-_tuxayo/ > Translation#Info_about_the_translation_toolchain Ran prove > /kohadevbox/koha/t/Koha/Auth/Permissions.t, could not replicate the failure. I wonder if it's worth apply the patch on current main, and running this again? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42187] New: Elasticsearch: Item type translations broken for facet descriptions
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42187 Bug ID: 42187 Summary: Elasticsearch: Item type translations broken for facet descriptions Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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: 38136 This affects both OPAC and staff with and without bug 38136: The item type descriptions are not showing translated, if translations have been set up in administration > itemtpes Test plan: * Set up your installation with Elasticsearch * Install at least one additional language. In ktd: sudo koha-translate --install de-DE --dev kohadev * Make sure the language is activated in the system preferences: - OpacLanguages - StaffInterfaceLanguages * Searchengine system preference: Elasticsearch * Go to administration > itemtypes * Translate one or more of the item into the installed language by - Edit itemtype X - Clicking on the "Translate into other languages" link * Search the catalog and notice the item type facet showing in the result list will remain in English in staff interface and OPAC when switching between translations. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38136 [Bug 38136] Refactor database translations (alternative) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 36357] New: Add Template::Toolkit filters for internationalization (I18N)
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36357 Bug ID: 36357 Summary: Add Template::Toolkit filters for internationalization (I18N) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr, jonathan.druart(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 52

[Bug 20784] New: Capture more changes in Logs
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20784 Bug ID: 20784 Summary: Capture more changes in Logs Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice to have an Administration Log. A log that tracks changes (add/modify/deletes) to branch information, itemtype information, circ rules, authorised_values (others areas). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 10190] Overdue notice triggers based on item type
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '26

26 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 --- Comment #615 from Chloé Zermatten <chloe.zermatten(a)openfifth.co.uk> --- (In reply to Victor Grousset/tuxayo from comment #614) > Thanks for the updated patches. I got this error with tests: > > kohadev-koha@kohadevbox:koha(testing-SO-QA)$ prove > /kohadevbox/koha/t/Koha/Auth/Permissions.t > /kohadevbox/koha/t/Koha/Auth/Permissions.t .. 1/4 > # Failed test 'Expected permissions generated for superlibrarian' > # at /kohadevbox/koha/t/Koha/Auth/Permissions.t line 314. > # Structures begin differing at: > # $got->{CAN_user_parameters_manage_circ_triggers} = '1' > # $expected->{CAN_user_parameters_manage_circ_triggers} = Does not > exist > # Looks like you failed 1 test of 1. > > I don't think is a setup step that should be missing. I started KTD with the > patches already. And redoing the updatedatabase doesn't help. > > ----- > > QA script reports this: > [FAIL] koha-tmpl/intranet-tmpl/prog/js/vue/stores/circulation-rules.js > FAIL forbidden_patterns > forbidden pattern: Use __("") instead of _("") (line 371) > > It's just this: > https://wiki.koha-community.org/wiki/User:Victor_Grousset_-_tuxayo/ > Translation#Info_about_the_translation_toolchain Re- QA script: it is picking up a regex (see https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190#c238) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 34757] New: Batch Item Deletion allow for Items with Holds to be deleted.
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34757 Bug ID: 34757 Summary: Batch Item Deletion allow for Items with Holds to be deleted. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl >From the bibliographic record with a hold on it, if a staff member tries to delete an item, they are denied due to the fact there is a hold on it. If a staff member from the bibliographic record, chooses to batch delete the items or uses the batch item deletion tool, this item will be deleted with no notice there is a hold. We should stay consistent on if Koha will allow for items to be deleted with a hold or not. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 8292] clicking ignore on hold cancels transfer
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '26

25 Mar '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8292 --- Comment #20 from trevor.diamond(a)mainlib.org --- My organization is looking to fund a development to fix this. Would anyone copied on this be interested in contributing? -- You are receiving this mail because: You are watching all bug changes.

1 0