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

[Bug 36372] New: Allow privileged users to set the 'record source' on cataloguing
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '26

22 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36372 Bug ID: 36372 Summary: Allow privileged users to set the 'record source' on cataloguing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This would be handy, as right now it can only be set through an API request. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 70

[Bug 18948] New: Elasticsearch - Reindexes should use aliases to avoid down time while reindexing
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '26

22 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18948 Bug ID: 18948 Summary: Elasticsearch - Reindexes should use aliases to avoid down time while reindexing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: nick(a)bywatersolutions.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This patchset aims to add the ability to leverage the ES alias feature during a reindex - when doing a full reindex or a deletion the indexer will look for an existing index under the alias - if not found it will create a new one, if found it will index into a new index and point the alias there when done and then delete the old index. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 35837] New: It would be useful to understand what plugins are being used in the wild.
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '26

22 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35837 Bug ID: 35837 Summary: It would be useful to understand what plugins are being used in the wild. 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org HEA hasn't seen much love of late.. it would be great to send back statistics on plugins used in an installation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 52

[Bug 39650] New: Updating the protected flag is not possible when creating a new patron
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '26

22 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39650 Bug ID: 39650 Summary: Updating the protected flag is not possible when creating a new patron Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: marion.durand(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When creating a new patron, it is not possible to update the protected flag even when logged in as a superlibrarian. It is still possible to update this flag when updating an existing patron. This seams liked to bug 36085. The check to set the authorization flag CanUpdateProtectPatron (witch restrict the update to only superlibrarian) is itself in a check for op 'edit_form', 'cud-save' or 'duplicate'. The flag CanUpdateProtectPatron is not passed to the template when creating a new user as the op is 'add_form' even when logged in as a superlibrarian. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 41946] New: Superlibrarian should be able to set protected status on patron creation
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '26

22 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41946 Bug ID: 41946 Summary: Superlibrarian should be able to set protected status on patron creation Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Since bug 36085, the protected flag in a patron account was removed from the patron creation form, regardless of if the user is a superlibrarian. 1. With a superlibrarian account, go to Patrons > New patron > Choose any category --> Before bug 36085 : In "Library management" section, there is a Protected yes/no field --> After bug 36085 : the Protected option is no longer there. If I create a SIP account, I now have to create the account, then go back an edit it to add the protection. Non-superlibrarians should still not be able to set the flag on creation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 16631] New: Show groups/categories of reports to authorized staff
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '26

22 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16631 Bug ID: 16631 Summary: Show groups/categories of reports to authorized staff Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org It would be helpful to have reports that are specific groups/categories to be authorized under the reports permissions in a patron account. Not everyone wants to see everyone else's reports, some are similar but are not. Some are for superlibrarians to test, and are not ready for use. It would be great if we could specify groups and even subgroups in the permissions that the staff could access, or specify all groups. All groups should be the norm for a superlibrarian. Christopher -- You are receiving this mail because: You are watching all bug changes.

1 299

[Bug 41771] New: Diff in syspref descriptions after Bug 30331
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '26

22 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41771 Bug ID: 41771 Summary: Diff in syspref descriptions after Bug 30331 Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org There is a diff in syspref's description for existing installs: # Failed test 'Comparing AutomaticRenewalPeriodBase' # at t/db_dependent/check_sysprefs.t line 135. # Structures begin differing at: # $got->{explanation} = 'Set whether the renewal date should be counted from the date_due or from the moment the Patron asks for renewal, for automatic renewals' # $expected->{explanation} = 'Set whether the renewal date should be counted from the date_due or from the moment the Patron asks for renewal, for automatic renewals ' # Failed test 'Comparing ManualRenewalPeriodBase' # at t/db_dependent/check_sysprefs.t line 135. # Structures begin differing at: # $got->{explanation} = 'Set whether the renewal date should be counted from the date_due or from the moment the Patron asks for renewal ' # $expected->{explanation} = 'Set whether the renewal date should be counted from the date_due or from the moment the Patron asks for renewal, for manual renewals ' # Looks like you failed 2 tests of 1753. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 42046] New: Bug 30331 database update is not idempotent
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '26

22 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42046 Bug ID: 42046 Summary: Bug 30331 database update is not idempotent Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The DBRev for Bug 30331 is not idempotent: my $base_period = C4::Context->preference('RenewalPeriodBase'); $dbh->do( q{ UPDATE systempreferences SET variable = 'ManualRenewalPeriodBase' WHERE variable = 'RenewalPeriodBase' } ); When ran twice: "ERROR: {UNKNOWN}: DBI Exception: DBD: :db do failed: Duplicate entry 'ManualRenewalPeriodBase' for key 'PRIMARY' at /kohadevbox/koha/C4/Installer.pm line 819" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 30331] New: Allow RenewalPeriodBase behavior to differ between manual and automatic renewals
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '26

22 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30331 Bug ID: 30331 Summary: Allow RenewalPeriodBase behavior to differ between manual and automatic renewals Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We should have a way to make auto-renewals and manual renewals follow different RenewalPeriodBase behavior. I'm working with a library that uses a mix of manual and automatic renewals. For items that auto-renew, the renewal happens two days before the item is due, so they want RenewalPeriodBase set to add time on to the existing due date so the patron gets their full renewal period. But for items renewed manually, they want RenewalPeriodBase set to calculate from the renewal date, though, so patrons can't renew early and lock in extra time with the item. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 53

[Bug 22637] New: Add ability to full reindex elasticsearch index from UI
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '26

22 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22637 Bug ID: 22637 Summary: Add ability to full reindex elasticsearch index from UI Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: josef.moravec(a)gmail.com Target Milestone: --- Button in toolbar on elastic search admin page to initiate full reindex. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10