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

[Bug 37512] New: Add a function to reset login attempts
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37512 Bug ID: 37512 Summary: Add a function to reset login attempts Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When a user tries to much login attempts, they are blocked. There are two ways to unlock the user: 1 - Change the database 2 - Reset the password There is currently no option to simply remove the lock for a blocked account. In BZ 25947 (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25947) we added a button to reset the password and another to simply reset the loginattempts. This bug has been created to split the two improvements. This bugs containts the improvements related to the button to reset loginattempts -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 12450] Easily close a branch
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12450 Elizabeth Hoffman <ehoffman(a)plumcreeklibrary.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ehoffman(a)plumcreeklibrary.n | |et -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 36085] New: Protected Status should come with a permission
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36085 Bug ID: 36085 Summary: Protected Status should come with a permission Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the new enhancement, 26170, add protected status to patrons, this allows any patron to be updated/edited to be a 'protected patron'. Staff with 'edit borrowers' permission will be able to update this status. I believe there should be a permission to allow for this field to be updated/edited within Koha. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

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

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 Michaela Sieber <michaela.sieber(a)kit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #316 from Michaela Sieber <michaela.sieber(a)kit.edu> --- General: Please revise the test plan, as it is no longer up to date. For example, overdue_X_has_rules no longer exists (Part 11.5) , and the permission is no longer available either (Part 10.1). We believe that this part is not testable at all: Part 13: Comparison with Legacy Interface 3. Verify it appears correctly in the old interface (if applicable) -- Strong contrasts and consistent color schemes for better understanding: Please use the same blue color as on circulation rules page due to poor contrast. Please use : rgb(218.1, 236.4, 251.4) = #DAECFB instead of : rgba(132, 193, 243, 1) = #84c1f3 ( this one is tooo dark) AND please use yellow color for Error Messages, as used elsewhere in Koha. -- Here are all the issues we found while going through the test plan. 1.) Still permission issues : Something went wrong: Error: Authorization failure. Missing required permission(s). --> Martin is working on this To fully use the CirculationTriggers app a user needs all of: circulate: circulate_remaining_permissions (read + write circ rules) parameters: manage_circ_rules (load the config/UI) catalogue: 1 (load item types and libraries) parameters: catalogue (load patron categories) 2.) Letter context it is not possible to select Letters with branchcode See Testplan - Part 3: Adding New Triggers - 4. Step 3 - Configure New Trigger - Verify only templates for the selected library context appear - Part 7: Context-Specific Behavior 1. Test library-specific letter filtering: - Create/edit a trigger for a specific library - Verify only letter templates with matching branchcode or default templates appear 3.) Editing Existing Triggers is not always possible editing the delay is only possible for all / all rules. have several rules for trigger 1 e.g. a all/all/all rule plus a all/Kids/Books with a different delay value (but same letter code as all/all/all rule) Now try to change the delay value. As soon as you press the submit button, you receive the following error message: "Your changes could not be saved as this circulation trigger was updated elsewhere. Please see the updated trigger below." See Testplan Part 4: Editing Existing Triggers 4.) Deletion of triggers does not delete all rules that are listed to reproduce: have several rules for trigger 2 e.g. a all/all/all rule plus a all/Kids/Books with a different delay value (but same letter code as all/all/all rule) --> Delete trigger, than the all/all/all rule is deleted and the entry for all/Kids/Books remains See Testplan: Part 5: Deleting Triggers 5.) No rules are displayed and syspref doesn't matter As soon as you access the page /cgi-bin/koha/admin/circulation_triggers, no rule sets are displayed; the list is empty. In addition, the system preference DefaultToLoggedInLibraryOverdueTriggers is not taken into account. See Testplan 3. Test DefaultToLoggedInLibraryOverdueTriggers preference: - Set preference to "Yes" - Reload circulation triggers page - Verify it defaults to your logged-in library - Set preference to "No" - Verify it defaults to "All libraries" -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 40738] New: Loan period by month as well as days and hours
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40738 Bug ID: 40738 Summary: Loan period by month as well as days and hours Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hdunne-howrie(a)westminster.gov.uk QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com To compliment the bookings module, we would love to see the option for loan periods to include Months as well as Days and Hours. This would help us as we loan out sheet music for a month at a time for which there is a checkout fee. At the moment we are having to use '30 days' but this isn't ideal as our actual procedure is for 1 month at a time, so a bit of a fudge. I suspect other libraries like us will have items they checkout that are loaned in months, not days, so I'm hoping useful for libraries beyond our own. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 41925] New: Curbside Pickup should also trigger SMS notices
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41925 Bug ID: 41925 Summary: Curbside Pickup should also trigger SMS notices Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: tech.aimee(a)salinapublic.org QA Contact: testopia(a)bugs.koha-community.org Currently, patrons are only notified by email when their pickups are scheduled. They should also be notified by SMS. It would also be great to be able to communicate when pickups are ready or cancelled. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 41924] New: Curbside Pickup - Cancellation should be able to be toggled off
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41924 Bug ID: 41924 Summary: Curbside Pickup - Cancellation should be able to be toggled off Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: tech.aimee(a)salinapublic.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com If patrons are able to cancel their pickups and information on cancelled pickups are not stored in the table, this can lead to scheduled pickups disappearing without tracking or explanation. Admins should be able to choose if patrons are able to cancel their pickups at all in the Koha configuration. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 41923] New: Curbside Pickup - Cancelled pickups should live in the database
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41923 Bug ID: 41923 Summary: Curbside Pickup - Cancelled pickups should live in the database Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: tech.aimee(a)salinapublic.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com If staff are staging items for patrons to be picked up, and the patron cancels, there is no documentation of what is going on with the pickup - it is just disappeared from the table. To prevent confusion, misplaced items, make notes on patrons accounts, etc., cancelled pickups should stay in the database. Perhaps just a cancelled_datetime column? It would also be great for pulling reports in the same manner as other services - how many pickups were cancelled, which were cancelled today so we can reset, how many times has a patron cancelled, and so on. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 39880] New: Add shelving location to cn_browser.tt
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39880 Bug ID: 39880 Summary: Add shelving location to cn_browser.tt Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be helpful to have a column for shelving location in the cn_browser results. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 41447] New: Provide an official bootstrap script to configure Koha APT repository on Debian/Ubuntu
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '26

26 Feb '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41447 Bug ID: 41447 Summary: Provide an official bootstrap script to configure Koha APT repository on Debian/Ubuntu Initiative type: --- Sponsorship --- status: Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Release tools Assignee: jonathan.druart(a)gmail.com Reporter: saiful(a)semanticconsulting.com Installing Koha on Debian and Ubuntu currently requires manually performing several prerequisite steps before koha-common can be installed, including: - Adding the Koha APT signing key - Configuring the Koha APT repository - Running apt update These steps are well documented, but they are repetitive, error-prone for new users, and frequently re-implemented across third-party guides and automation scripts. This bug proposes providing an official, minimal bootstrap script for Debian/Ubuntu only, whose sole responsibility is to: - Install the Koha APT signing key - Configure the Koha APT repository - Run apt update After this step, installation continues exactly as required: apt install koha-common Rationale / Motivation: - Reduces installation friction for first-time and test installations on supported platforms - Encourages a single, auditable implementation instead of many unofficial ones - Simplifies automation, CI, containers, and provisioning workflows - Keeps Koha's existing packaging and installation model unchanged Reference Implementation: A reference implementation currently used in production for ~2 years is available here: https://github.com/saiful-semantic/KohaOnUbuntu This is provided to illustrate the approach, not as a final implementation. The reference implementation is validated using GitHub Actions CI on both Ubuntu LTS (20.04, 22.04, 24.04) and Debian (11, 12). Security Considerations: The common 'curl | sudo bash' pattern is acknowledged as a concern, which can be mitigated by: - Hosting the script under an official Koha domain - Providing checksums or signature verification Alternatively, offering a download-then-execute workflow instead of piping. -- You are receiving this mail because: You are watching all bug changes.

1 4