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

[Bug 39670] New: CircConfirmItemParts in SCO should allow option for blocking checkout or just warning patron
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '26

24 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39670 Bug ID: 39670 Summary: CircConfirmItemParts in SCO should allow option for blocking checkout or just warning patron Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Right now, if CircConfirmItemParts is on and a patron using SCO attempts to checkout an item with a material note they see "Item must be checked out at a circulation desk." It would be nice if there was an option to confirm the circ parts, not just block. Maybe something to build on top of Bug 34643 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 41780] New: Show firstname if preferred_name is empty in moremember.tt
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '26

24 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41780 Bug ID: 41780 Summary: Show firstname if preferred_name is empty in moremember.tt Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: ayoub.glizi-vicioso(a)inLibro.com Reporter: ayoub.glizi-vicioso(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Depends on: 28633 Since bz28633, the patron's firstname is no longer displayed in the staff interface (moremember.tt) if the 'preferred_name' field is NULL or empty. This issue occurs when patrons are imported via external scripts (like Activitek) that do not automatically populate 'preferred_name' with the 'firstname' value. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 [Bug 28633] Add a preferred name field to patrons -- You are receiving this mail because: You are watching all bug changes.

1 77

[Bug 43631] New: Add widget for supplying/lending ill requests on ill homepage
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '26

24 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43631 Bug ID: 43631 Summary: Add widget for supplying/lending ill requests on ill homepage Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com Target Milestone: --- -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 43630] New: Check in table should link back to ILL if the checkout/hold was associated with an ILL request
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '26

24 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43630 Bug ID: 43630 Summary: Check in table should link back to ILL if the checkout/hold was associated with an ILL request Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com, pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com Target Milestone: --- It would great if we could get back to a linked ILL request from the checkin page if you have the biblio linked to the request. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 0

[Bug 43629] New: Changes to patron categories are not logged
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '26

24 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43629 Bug ID: 43629 Summary: Changes to patron categories are not logged Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- We set a lot of important things in the patron categories, but we don't log any changes to those. We really should log those changes -- including changes to things like category default messaging preferences that aren't directly in the categories table. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 42689] New: How to handle English ILL status names in translation?
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '26

24 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42689 Bug ID: 42689 Summary: How to handle English ILL status names in translation? Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: caroline.cyr-la-rose(a)inlibro.com, f.demians(a)tamil.fr, jonathan.druart(a)gmail.com, julian.maurice(a)biblibre.com Depends on: 37762 While translating the new strings from bug 37762 in main I noticed that often status are mentioned that look like codes. I am not sure if they should be translated and how to best handle them in translations to make the purpose clear to users. If they are codes that should not be translated some context might be helpful or maybe some should be re-worded? Collecting here to get some guidance/ideas. The supplying library cannot fill the request based on information provided or may be able to supply at a later date. Additional information is provided in the RetryInfo section. The requesting library may submit a Retry request which may include updated information koha-tmpl/intranet-tmpl/prog/js/vue/components/ILL/SupplyingResource.vue:255 CopyOrLoan koha-tmpl/intranet-tmpl/prog/js/vue/components/ILL/SupplyingResource.vue:532 • koha-tmpl/intranet-tmpl/prog/js/vue/components/ILL/SupplyingResource.vue:1089 The supplying library cannot fill the request. The explanation may be provided in the ReasonUnfilled data element koha-tmpl/intranet-tmpl/prog/js/vue/components/ILL/SupplyingResource.vue:559 Update this request's status to <strong>WillSupply </strong>? koha-tmpl/intranet-tmpl/prog/js/vue/components/ILL/SupplyingResource.vue:205 The supplying library cannot fill the request. The explanation may be provided in the ReasonUnfilled data element koha-tmpl/intranet-tmpl/prog/js/vue/components/ILL/SupplyingResource.vue:559 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37762 [Bug 37762] Expand ILL to allow for supplying agency/lending library workflows -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 42470] New: Changes to patron messaging preferences should be logged
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '26

24 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42470 Bug ID: 42470 Summary: Changes to patron messaging preferences should be logged Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com When troubleshooting account notification issues, it would be really helpful to have action logs on any changes to patron messaging preferences. This would allow you to see if a patron's preferences have changed recently and easily identify which notifications a patron should have been receiving at a given point in time. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 14806] Action Log for Modifying borrower messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '26

24 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14806 hebah(a)bywatersolutions.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emily.lamancusa@montgomeryc | |ountymd.gov --- Comment #16 from hebah(a)bywatersolutions.com --- *** Bug 42470 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 14806] Action Log for Modifying borrower messaging preferences
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '26

24 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14806 Danielle M. <dmeininger591(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmeininger591(a)gmail.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 43628] New: Returning a lost item may not charge overdue fine when item has historical LOST overdue from another patron
by bugzilla-daemon＠bugs.koha-community.org 24 Sep '26

24 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43628 Bug ID: 43628 Summary: Returning a lost item may not charge overdue fine when item has historical LOST overdue from another patron Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: Laura.escamilla(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com Target Milestone: --- When lostreturn = charge, returning a lost item should calculate and charge the patron an overdue fine. However, if the same item has a historical OVERDUE accountline with status = LOST belonging to a previous patron, Koha may use that previous patron when processing the current lost-item return. The current patron's LOST and PROCESSING charges are refunded correctly, but the new overdue fine is not created. This has been reproduced with two patrons using the same item across separate checkout/lost/return cycles. Relevant configuration --CalculateFinesOnReturn = 1 --CalculateFinesOnBackdate = 1 --WhenLostForgiveFine = 1 --BlockReturnOfLostItems = 0 --lostreturn = charge --processingreturn = refund --Fine = 0.25 --Overdue fines cap = 5.00 Steps to reproduce 1. Create Patron A and Patron B. 2. Check an item out to Patron A with a due date sufficiently in the past to generate an overdue fine. 3. Generate the overdue fine for Patron A. 4. Mark the item lost. 5. Confirm Patron A's OVERDUE accountline is now: - status = LOST - amountoutstanding = 0 6. Return the item. 7. Confirm the historical OVERDUE / LOST accountline remains associated with the item. 8. Check the same item out to Patron B with a due date in the past. 9. Do not generate an overdue accountline for Patron B before marking the item lost. 10. Mark the item lost so LOST and PROCESSING charges are created for Patron B. 11. Return the item. Expected result: The current LOST and PROCESSING charges are refunded and Patron B receives the appropriate overdue charge according to the circulation rules. For example: LOST_FOUND -10.00 PROCESSING_FOUND -5.00 OVERDUE 5.00 RETURNED Actual result: The LOST and PROCESSING charges are refunded: LOST_FOUND -10.00 PROCESSING_FOUND -5.00 but no new OVERDUE accountline is created for Patron B. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1