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

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

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 --- Comment #952 from Pedro Amorim (ammopt) <pedro.amorim(a)openfifth.co.uk> --- Thanks everyone! Pushed to main for 26.11! -- 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 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10190 Pedro Amorim (ammopt) <pedro.amorim(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Version(s)| |26.11.00 released in| | Status|Passed QA |Pushed to main -- You are receiving this mail because: You are watching all bug changes.

1 0

[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

[Bug 36352] New: Allow agreements to have multiple vendors
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36352 Bug ID: 36352 Summary: Allow agreements to have multiple vendors Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: billieanne.gebb(a)frontier.edu CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com Some agreements may have multiple vendor relationships, for example, a title could be published by one entity but billed through another. It would be helpful to have both listed with the agreement. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 41640] New: Optional way to log multiple local uses with statistical patron
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41640 Bug ID: 41640 Summary: Optional way to log multiple local uses with statistical patron Initiative type: --- Sponsorship --- status: 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: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Libraries would like a way to be able to optionally count multiple local uses at once, especially for workflows where things are recorded at end of day. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 43506] New: Add a way to copy opening hours from one library to another
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43506 Bug ID: 43506 Summary: Add a way to copy opening hours from one library to another Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Depends on: 43492 Target Milestone: --- There is currently no way to copy a library's opening hours (Bug 43492) to another library. A multi-branch system where several service points share identical hours (a consortium, or a new library going live with the same hours as a sister branch) has to re-enter every weekday/time-range/type combination by hand. Koha::Library::Calendar already solves the equivalent problem for holiday closures via copy_to and the REST /libraries/{id}/calendar/copy endpoint (Bug 42311). Opening hours should offer the same capability: a Koha::Library::OpeningHours->copy_to method, a REST endpoint following the same shape, and a UI action alongside the existing hours editor in Administration -> Libraries. Test plan: 1. Set up opening hours for library A, including at least one multi-day linked span. 2. Copy library A's hours to library B via the new action. 3. Confirm library B now has the same hours, correctly re-linked (not pointing at library A's row ids). 4. Confirm re-running the copy does not create duplicates. Depends on Bug 43492. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43492 [Bug 43492] Normalize library opening hours into a dedicated library_opening_hours table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 43494] New: Add REST API endpoints for library opening hours
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43494 Bug ID: 43494 Summary: Add REST API endpoints for library opening hours Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)openfifth.co.uk QA Contact: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com Depends on: 43492 Target Milestone: --- Bug 37617 asks for library opening hours to be available via the REST API - either embedded in /libraries responses or via a dedicated endpoint - noting that the current /libraries embed exposes library_hours as an untyped array with no write access at all; hours can currently only be edited through the admin/branches.pl form. Building on the library_opening_hours facade from Bug 43492, this bug adds full CRUD for library opening hours as a REST sub-resource of /libraries (mirroring the pattern used for library calendar closures in Bug 42311), plus a typed schema for the existing /libraries embed, so opening hours are available both ways rather than having to choose one. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43492 [Bug 43492] Normalize library opening hours into a dedicated library_opening_hours table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 43492] New: Normalize library opening hours into a dedicated library_opening_hours table
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43492 Bug ID: 43492 Summary: Normalize library opening hours into a dedicated library_opening_hours table Initiative type: --- Sponsorship --- status: Product: Koha Version: Main 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)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Library opening hours (Bug 6796) are stored in a single library_hours table with a composite (library_id, day) primary key: exactly one row per weekday per library. This makes it structurally impossible to record more than one opening/closing pair per day (Bug 37616, Bug 37708), and there is no way to represent hours that open on one day and don't close again until a later day (raised as a concern on Bug 36596 against a simple "open and close must always be set together" rule). The Koha::Library::Hour(s) object classes are empty shims with no validation, and there is no relationship at all between these hours and the library Calendar (weekly/repeating/single closures, Bug 42310/42314/42311), which is the underlying problem in Bug 36079. This is the first of a small dependent series that replaces library_hours with a normalized model. This bug covers the schema and object layer: - A new library_opening_hours table, allowing any number of rows per (library, weekday), with an explicit closes_opening_id self-reference so a slot that opens on one day and doesn't close until a later day is represented as two clearly linked rows rather than by guesswork or an offset column. - A new OPENING_HOURS_TYPE authorised value category (seeded with a reserved GENERAL value) so hours can be grouped by what they're for (Bug 37708), reusing Koha's existing authorised values admin screen rather than a bespoke vocabulary. - A Koha::Library::OpeningHours facade (mirroring Koha::Library::Calendar) providing validated CRUD and interval resolution. Migration of existing library_hours data to type GENERAL is included. Follow-up bugs build the Koha::Library accessor and Calendar linkage, REST API, circulation integration, and the admin interface on top of this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 43286] New: Rephrase "Target item/record is an invalid pickup location"
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43286 Bug ID: 43286 Summary: Rephrase "Target item/record is an invalid pickup location" Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: Academy Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Translating this I have been wondering how an item/record can be a pickup location and what is meant here. koha-tmpl/intranet-tmpl/prog/en/modules/reserve/request.tt:229 Target item/record is an invalid pickup location -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 42722] New: Improve invalidPickupBranch error message
by bugzilla-daemon＠bugs.koha-community.org 10 Sep '26

10 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42722 Bug ID: 42722 Summary: Improve invalidPickupBranch error message Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: ephetteplace(a)cca.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com See Bug 41879 which fixes an issue where a hold can be moved to a bib owned by a branch that doesn't allow pickup at the original hold pickup location. The current error message reads: "Target item/record is an invalid pickup location". This is a bit awkward as it says the item/record _is_ a location. I'll brainstorm some other possibilities below. "Target item/record would have an invalid pickup location" "Hold is unable to be fulfilled using its original pickup location" Or something that tells you how to address the underlying issue? "Target item/record would have an invalid pickup location. Please move the hold to a different item/bib or change the pickup location of the hold to a valid one." I realize the last is the most verbose, but I do like the idea of providing solutions with the error message. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30