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

[Bug 33312] New: Add circulation and fines rules table from smart-rules.pl to column settings
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33312 Bug ID: 33312 Summary: Add circulation and fines rules table from smart-rules.pl to column settings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be very helpful to be able to configure hiding columns as libraries rarely (if ever) use all the columns (suspensions vs fines, etc.) Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 40076] New: Add --skip-no-email parameter to borrowers-force-messaging-defaults.pl
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40076 Bug ID: 40076 Summary: Add --skip-no-email parameter to borrowers-force-messaging-defaults.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities 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: robin(a)catalyst.net.nz I use this script a lot during migrations to set the default preferences from the categories to all the patrons. However, recently I've had cases where about half the patrons did not have email addresses in their accounts. This means that I either set everyone's preferences and the library has to go back and remove the preferences from the patrons without email addresses, or I don't do it, and the library has to set the preferences for those with email addresses. (I think I've had back-to-back cases like this because in their old system it was set up as if the patron has an email address, they get the email notices, and if they want to opt-out, they remove their email address from their account.) It would be great if the script could skip the patrons without email addresses. (Note : we never set SMS messages by default, only email; I don't know if someone does this, but it is not a requirement for us to manage sms messaging with this script.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 39781] New: Cannot limit by library when creating custom patron email sent via patron details page
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39781 Bug ID: 39781 Summary: Cannot limit by library when creating custom patron email sent via patron details page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 29393 To recreate: 1 - create a new notice in module "Patrons (custom message)" 2 - limit your notice to a library 3 - give your notice content for the email format 4 - go to a patron record, select Add Message 5 - confirm the notice you created appears as an option regardless of whether or not you're logged in at the branch you selected in step 2 6 - confirm the Save button fails to enqueue your notice, regardless of logged-in branch We don't pass any branchcode along with the borrowernumber and letter_code when enqueueing this, so it fails if the notice template is limited to a branch. We should send the logged-in library when enqueueing the notice. We should also high the notice from the Add Message form if the user is not logged in at the correct branch. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29393 [Bug 29393] Ability to send emails from patron details page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 42083] New: Email and SMS messages from patron record should have distinct permissions
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42083 Bug ID: 42083 Summary: Email and SMS messages from patron record should have distinct permissions Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 40933, 29393 Bug 29393 added the ability to send email from a patron's record. 40933 expanded that to SMS. But they currently share a single permission. It would be preferable for those to be two distinct permissions. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29393 [Bug 29393] Ability to send emails from patron details page https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40933 [Bug 40933] Add SMS support under Add message feature -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 41920] New: Limit number of concurrent reports that can be run simultaneously for an instance of Koha
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41920 Bug ID: 41920 Summary: Limit number of concurrent reports that can be run simultaneously for an instance of Koha Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com As a continuation of bug 41919, we should limit the total number of simultaneous reports that can be run at a time. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 39207] New: Improve usability of search when holding a specific item
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39207 Bug ID: 39207 Summary: Improve usability of search when holding a specific item Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lauri.hanninen(a)lahti.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 178779 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=178779&action=e… Image showing how user's set library blocks filtering due to allowed pickup locations When filtering for a specific item on holds page using the search bar, it's currently not feasible to filter by user's set library. When entering the user's set library in the search field, search results won't narrow down because they include the active selection in the Allowed pickup locations column which by default is the user's set Library. Filtering by user's own library would be one of the common usages for the search field when placing a hold on a specific item, so it would have more usability if it could be fixed. See attached image as an example. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 42344] New: Remove CircSidebar
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42344 Bug ID: 42344 Summary: Remove CircSidebar Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: jonathan.druart(a)gmail.com Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 42330, 16530, 31403 Now that we can collapse the sidebar on all views (see bug 42330) we can remove the pref CircSidebar. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16530 [Bug 16530] Add a circ sidebar navigation menu https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31403 [Bug 31403] Activate circulation sidebar (CircSidebar system preference) on default in new installations https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42330 [Bug 42330] Use main-container.inc from all the templates -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 42296] New: Tidy all script tags - trivial ones
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42296 Bug ID: 42296 Summary: Tidy all script tags - trivial ones Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified 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: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 42094 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42094 [Bug 42094] Tidy all script tags (except value_builder) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 41318] New: AmazonLocale system preference - add Brazil as an option
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41318 Bug ID: 41318 Summary: AmazonLocale system preference - add Brazil as an option Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org See the post on Mattermost chat https://chat.koha-community.org/koha-community/pl/7mr33cigziruzpjsutpy97acka on 27 November 2025: amandap Hello Kohers <3, I would like to propose an enhancement to the AmazonLocale System Preference to include Brazil (amazon.com.br) as a selectable option. Currently, the system preference does not list a Brazilian locale. Brazilian libraries using Koha are forced to select the US (amazon.com) or another locale, which results in a low cover image match rate for Brazilian Portuguese editions, as our editions often differ significantly from those listed in other Amazon stores. Including amazon.com.br would significantly improve the accuracy of cover images displayed on the OPAC and Staff Interface for libraries operating in Brazil and potentially other Portuguese-speaking countries, enhancing the value of the Enhanced Content feature for this region. Thank you for considering this enhancement. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 35145] New: Add ability to order patron attributes
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35145 Bug ID: 35145 Summary: Add ability to order patron attributes Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org Right now, patron attributes are presented in code order. It would be nice to have a way to choose the order in which they are presented. I put this in OPAC because I noticed this in the self-registration form. But I guess it would be true for the staff interface too. My actual use case was for birth details of a baby. I had the birthdate, the number of weeks and the number of days of pregnancy, the weight of the baby, the surname of the baby, etc. I had specifically added them in the order I wanted because I thought the creation order would be the display order. But they were displayed in code order, and the order made no sense (file number, number of days of pregnancy, birth date of the baby, surname of the baby, weight at birth, number of weeks of pregnancy). I thought something like a "Display order" field like the ones we have in serial patterns and numbering and in the additional contents would be useful. To recreate: 1. Create several patron attributes with various codes 1.1. Go to Administration > Patron attribute types > New patron attribute type 1.2. Fill out the form - Code: enter any code, for example WEIGHT - Description: enter any description - Display in OPAC: check - Editable in OPAC: check 1.3. Click Save 1.4. Repeat to add a second code with a code alphabetically "before" the previous one, for example SURNAME 1.5. Optionnally, add more to really view the order 2. Enable self-registration 2.1. Go to Administration > System preferences 2.2. Search for selfreg 2.3. Set PatronSelfRegistration to Allow 2.4. Set a category in PatronSelfRegistrationDefaultCategory 2.5. Click Save all OPAC preferences 3. View self-registration form 3.1. Go to the OPAC 3.2. Click on Don't have an account? Register here. 3.3. Go to the bottom of the form --> Note that the patron attribute fields are presented in alphabetical order of the code. -- You are receiving this mail because: You are watching all bug changes.

1 171