May 2025 - Koha-bugs - lists.koha-community.org

[Bug 38308] New: Add validation to 'booking pre/post-processing' in circulation rules
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38308 Bug ID: 38308 Summary: Add validation to 'booking pre/post-processing' in circulation rules Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 34440 We should validate the input fields so only numeric values can be entered. Right now a "k" or anything else will be happily saved without warning. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34440 [Bug 34440] Add warm-up and cool-down periods to bookings -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 38016] New: Relabel booking precaution column heading in circulation rules tables
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38016 Bug ID: 38016 Summary: Relabel booking precaution column heading in circulation rules tables Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 34440 In the circulation rules there are 2 tables with 2 new columns named: * booking preparation period * booking precaution period While the first is before the booking, the second is after the booking is returned, but that's not clearly reflected in the name. Some alternative suggestions we came up with: A) * booking lead period * booking trail period B) * booking warm-up period * booking cool-down period C) * booking pre-buffer (days) * booking post-buffer (days) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34440 [Bug 34440] Add warm-up and cool-down periods to bookings -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 36536] New: Make REST API's validateUserAndPassword update borrowers.lastseen
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36536 Bug ID: 36536 Summary: Make REST API's validateUserAndPassword update borrowers.lastseen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no CC: tomascohen(a)gmail.com Since ILS-DI (which specifically means the AuthenticatePatron verb) is an option that can be selected for TrackLastPatronActivityTriggers, I would expect the validateUserAndPassword of the REST API to also contribute to updating borrowers.lastseen. Since there is no separate option for activalting it, I thought maybe the REST API is considered so much "core" to Koha that the logins are tracked when "Logging in" is activated as an option for TrackLastPatronActivityTriggers. But it looks like it is not. To reproduce in KTD: TrackLastPatronActivityTriggers = [Select all] RESTBasicAuth = Enable Check the lastseen value of the "koha" user in the database: select borrowernumber, lastseen from borrowers where borrowernumber = 51; The value should be NULL, or some past timestamp. Run this script: https://wiki.koha-community.org/wiki/REST_API:_Checking_username_and_passwo… Check the lastseen value of the "koha" user again. I would expect it to have been updated when the script ran, but it is not. Not sure if validateUserAndPassword should be considered as just another way of "Logging in", or if it should be a separate option for TrackLastPatronActivityTriggers, but the latter would give maximum flexibility. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 32

[Bug 37651] New: biblio->current_holds and item->current_holds do not respect ConfirmFutureHolds
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37651 Bug ID: 37651 Summary: biblio->current_holds and item->current_holds do not respect ConfirmFutureHolds 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com See also bug 37650. When we consider ConfirmFutureHolds to build the holds to pull list, we actually could say that these holds, probably only one or two days ahead, are current holds too. Currently, they are just completely ignored. But e.g. having a library depot further away require collecting those items earlier etc. At least the majority of calls look like they could use the lookahead days from ConfirmFutureHolds. Filed as enh, but very close to a bug. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 57

[Bug 36278] New: Relabel "Gone no address"
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36278 Bug ID: 36278 Summary: Relabel "Gone no address" Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Many libraries find the "Gone no address" patron account flag awkwardly phrased/named. Perhaps "Address block", "Wrong address", "Address correction needed", or similar would more clearly indicate to library staff what this flag does. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 39883] New: NEW_SUGGESTION email notices end up in the patrons notice tab (members/notices.pl) when they should not
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39883 Bug ID: 39883 Summary: NEW_SUGGESTION email notices end up in the patrons notice tab (members/notices.pl) when they should not Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org To recreate: 1. Turn on EmailPurchaseSuggestions and add an email address to EmailAddressForSuggestions. 2. Create a new suggestion and set the " Created by:" field to a patron with an email address 3. Check the message queue ( select * from message_queue where letter_code = "NEW_SUGGESTION" ) 4. There is a NEW_SUGGESTION queued, the to_address should be the email you entered in EmailAddressForSuggestions. 5. The borrowernumber is the borrower who made the suggestion. This shouldn't end up in the notice tab for the borrower since these notices are for staff. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 39824] New: Add a direct link to default framework in MARC bibliographic frameworks page
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39824 Bug ID: 39824 Summary: Add a direct link to default framework in MARC bibliographic frameworks page Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In Administration > MARC bibliographic frameworks, add a direct link to default framework can be very useful. Currently one needs to move to the actions button, click to open it, and click on "MARC Structure". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 38997] New: Remove reference to "members" in SendAlerts
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38997 Bug ID: 38997 Summary: Remove reference to "members" in SendAlerts Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Developer documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org In SendAlerts documentation, it says "- notify patrons when their account is created (members)" but that documentation is out of date. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 36453] New: BlockExpiredPatronOpacActions should allow multiple actions options
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36453 Bug ID: 36453 Summary: BlockExpiredPatronOpacActions should allow multiple actions options Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 34597 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34597 [Bug 34597] Expired patrons can still place ILL requests through OPAC -- You are receiving this mail because: You are watching all bug changes.

1 79

[Bug 32604] New: Patron categories upper age limit not respected when creating a patron
by bugzilla-daemon＠bugs.koha-community.org 10 Oct '25

10 Oct '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32604 Bug ID: 32604 Summary: Patron categories upper age limit not respected when creating a patron Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: emmi.takkinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Koha treats patron categories upper age limit inconsistently. E.g. if child patron category's upper age limit is 18, one is still able to add child patron who is 18 years old. However, when cronjob update_patrons_category.pl is run, patrons over and exactly aged 18 are considered overaged and their categorycode is updated. We should either fix patron creation or cronjob to avoid confusion. To test: 1. Add upper age limit as 18 for child patron category. 2. Create a child patron whose age is 18. 3. Save. => Patron is saved successfully. 4. Run cronjob update_patrons_category.pl with verbose option. perl update_patrons_category.pl --too_old --from CHILD --to ADULT -v => Note that patron is reported as updated (or would have updated) as an adult patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22