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

[Bug 6532] Way to move items to another record in batches
by bugzilla-daemon＠bugs.koha-community.org 07 May '26

07 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6532 Thibaud Guillot (thibaud_g) <thibaud.guillot(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |42548 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42548 [Bug 42548] Add possibility to list multiple barcodes or one biblionumber on attach item action -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 40159] New: When modifying a subscription with received issues, prediction pattern doesn't start from next issue date
by bugzilla-daemon＠bugs.koha-community.org 07 May '26

07 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40159 Bug ID: 40159 Summary: When modifying a subscription with received issues, prediction pattern doesn't start from next issue date Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org To reproduce the issue : Make a record and create a subscription for this record with a week or month subscription length and a first issue date in the past (like 2016). Receive at least one issue. Edit the subscription and test the prediction pattern. The displayed prediction shows only one number (unless you set the subscription length for like a thousand issues). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 41017] New: Show if item is on hold even if OverduesBlockRenewing is on
by bugzilla-daemon＠bugs.koha-community.org 07 May '26

07 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41017 Bug ID: 41017 Summary: Show if item is on hold even if OverduesBlockRenewing is on 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com I've had a comment by a library that uses OverduesBlockRenewing as well as AllowRenewalLimitOverride (and AllowRenewalOnHoldOverride) that when the item is overdue, the fact that it's on hold is not displayed in the patron's checkouts. Their issue is that while they don't want patrons renewing overdue items from the OPAC, they sometimes override the renewal in the staff interface, but end up unknowingly renewing something that is on hold... To recreate in main: 1. Go to a patron's account and checkout with a past date to create an overdue checkout 2. Place a hold for the same item for another patron 3. View the first patron's checkouts --> In the "Renew" column, it says "On hold" 4. Enable AllowRenewalOnHoldOverride 5. Go back to the patron's checkouts --> The "Renew" column should still say "On hold" 6. Check the "Override renewal restrictions" box --> A check box appears in the "Renew" column, which still displays "On hold" nonetheless 7. Enable OverduesBlockRenewing ("block renewing for all the patron's items") (I think both blocks should work in this scenario, but the library has it set to all) 8. Enable AllowRenewalLimitOverride 9. Go back to the patron's checkouts --> The "Renew" column displays "Not allowed: overdue" (OK) No mention of on hold (NOT OK?) 10. Check the "Override renewal restrictions" box --> A check box appears in the "Renew" column (OK), still no mention of on hold (NOT OK?) The "On hold" mention should be displayed whether or not the item is overdue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 37

[Bug 41208] New: Log viewer should use an API or limit max results per search
by bugzilla-daemon＠bugs.koha-community.org 07 May '26

07 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41208 Bug ID: 41208 Summary: Log viewer should use an API or limit max results per search Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Koha's log viewer loads all results at one time into a datatable. Large systems can have potentially hundreds of millions of rows. An unconstrained search can easily use up all the RAM even on systems with dozens of gigbytes of memory. Koha should either have a limit of the query and encourage users to limit their query further if the full results cannot be displayed, or we should use the API for paginated results. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 42546] New: Unify language in system preferences that refer to Reply-To addresses
by bugzilla-daemon＠bugs.koha-community.org 07 May '26

07 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42546 Bug ID: 42546 Summary: Unify language in system preferences that refer to Reply-To addresses Initiative type: --- Sponsorship --- status: Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: david_liddle(a)sil.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Preface: I acknowledge the utility of using a different form, i.e. "ReplyTo", in variables instead of the official message header term "Reply-To". There are discrepancies in the text of system preferences that refer to Reply-To addresses. They can be found in both the staff interface and in the 'explanation' column of the 'systempreferences' table. These differences can make it difficult to find the relevant preferences/variables. (Some quotes below shortened for brevity.) AcquisitionsDefaultReplyTo UI: "Use the reply-to email address ___ when sending acquisitions order and claim notices. If left empty, it will fall back to the first defined address in the following list: library reply-to, library email, ReplytoDefault, KohaAdminEmailAddress." DB" "Default email address used as reply-to for notices sent by the acquisitions module." AddressForFailedOverdueNotices UI: "If left empty then it will fallback to the first defined address in the following list: Library ReplyTo, Library Email, ReplytoDefault and KohaAdminEmailAddress" DB: "If left empty then it will fallback to the first defined address in the following list: Library ReplyTo, Library Email, ReplytoDefault and KohaAdminEmailAddress" emailLibrarianWhenHoldIsPlaced UI: "The first email address set from this list will be used: library reply-to, library email, ReplytoDefault, KohaAdminEmailAddress." (NOTE: Inconsistent also in "first email address set from this list" versus "first defined address in the following list") DB: "If ON, emails the librarian whenever a hold is placed" (NOTE: No reference to Reply-To or the list.) ExpireReservesAutoFillEmail UI: "If no address is defined here, the email will be sent to the library's reply-to address." DB: "If not defined, Koha will fallback to the library reply-to address" ReplytoDefault UI: "Email address to be set as the replyto in emails:" DB: "The default email address to be set as replyto." SerialsDefaultReplyTo UI: "Use the reply-to email address ___ when sending serial claim notices. If left empty, it will fall back to the first defined address in the following list: Library ReplyTo, Library Email, ReplytoDefault, KohaAdminEmailAddress." DB: "Default email address used as reply-to for notices sent by the serials module." Consistent, accurate language and terminology matters, so I suggest dropping the hyphen only in direct references to variables that do not use it. Otherwise, the term should be represented as "Reply-To" as given in the RFC and as shown in a library's settings. It will improve searches and make recognition faster. (The same could be said for Return-Path.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 31900] New: Add support for logout from external OAuth2/OIDC identity providers
by bugzilla-daemon＠bugs.koha-community.org 07 May '26

07 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31900 Bug ID: 31900 Summary: Add support for logout from external OAuth2/OIDC identity providers Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 34806] New: Identity Provider Single-Logout Enhancement
by bugzilla-daemon＠bugs.koha-community.org 07 May '26

07 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34806 Bug ID: 34806 Summary: Identity Provider Single-Logout Enhancement Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: agostino.nigro(a)nigroweb.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Request enhancement to Identity Provider in Koha to support and setup Single-Logout so that when a user signs out of Koha they also logout of the Identity Provider be that ADFS, Azure, Okta, Etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 42307] New: Update patron card creator pages to use grid layout for forms
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42307 Bug ID: 42307 Summary: Update patron card creator pages to use grid layout for forms Initiative type: --- Sponsorship Sponsored status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 41823 - patroncards/edit-batch.tt - patroncards/edit-layout.tt - patroncards/edit-profile.tt - patroncards/edit-template.tt - patroncards/manage.tt - patroncards/print.tt Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41823 [Bug 41823] Update acquisitions admin pages to use grid layout for forms -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 42544] New: Cannot delete hold after checking out an item
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42544 Bug ID: 42544 Summary: Cannot delete hold after checking out an item Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: bdaeuber(a)cityoffargo.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com If you check out an item to a patron, then try to delete a hold from the holds tab, the deletion will fail. This is somewhat similar to bug 41211. To recreate: 1. Place an item on hold for a patron. 2. Navigate to the patron account. 3. Check out a different item. 4. Then go to the holds tab and click the trash can. Confirm the deletion. 4a. This forwards you to circulation.pl, but with a blank borrower number in the address bar 5. Return to patron account and note the hold has not been deleted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 21004] New: Use modal to add and edit notes on receiving orders/shipments page
by bugzilla-daemon＠bugs.koha-community.org 06 May '26

06 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21004 Bug ID: 21004 Summary: Use modal to add and edit notes on receiving orders/shipments page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org See bug 20969, but for parcel.pl. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13