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

[Bug 42826] New: Reports: Allow transfer/adoption of report ownership
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42826 Bug ID: 42826 Summary: Reports: Allow transfer/adoption of report ownership 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com Target Milestone: --- Bug 42667 introduces the edit_all_reports permission, restricting report editing to the report's creator unless the librarian holds that permission. This surfaces a gap: there is currently no mechanism to change the borrowernumber recorded as a report's owner. Two common real-world scenarios are blocked without this: 1. Staff departure. A librarian leaves the organisation. Their reports become ownerless (if the patron record is deleted) or remain locked to a departed account. Other staff with create_reports but not edit_all_reports cannot maintain them. 2. Adoption of ownerless/legacy reports. Reports created before ownership tracking was tightened, or imported via Mana, may have no owner. A librarian who wants to claim such a report and take ongoing responsibility for it has no way to do so without involving a superlibrarian. Proposed behaviour: - On the report edit form and/or via a dedicated action in the saved-reports list, a librarian holding edit_all_reports should be able to reassign the report's owner to any other staff patron, or clear the owner field. - A bulk-transfer option for the staff-departure case: reassign all reports owned by patron X to patron Y. This could live in the patron deletion workflow or in the reports administration area. - A librarian without edit_all_reports should be able to adopt an ownerless report (setting themselves as owner), since this is a tightening of access rather than a loosening. Acceptance criteria: - Single-report ownership transfer, restricted to edit_all_reports holders - Ownerless-report adoption available to any create_reports holder - Bulk transfer (move all reports from patron A to patron B), restricted to edit_all_reports holders -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 26355] New: Tie account renewals to patron modification requests
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26355 Bug ID: 26355 Summary: Tie account renewals to patron modification requests 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Allow patrons renewal reminders to link to the patron modification requests, asking them to review their information and make any any necessary updates if necessary, but acknowledging that the information is up to date. Create a check-box stating that they have reviewed all their information, and it is accurate and up to date (if no changes are made). Perhaps this check-box only shows when their account is due for renewal. -- You are receiving this mail because: You are watching all bug changes.

1 265

[Bug 36583] New: MEMBERSHIP_RENEWED message for manual renewals
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36583 Bug ID: 36583 Summary: MEMBERSHIP_RENEWED message for manual renewals Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: sbrown(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Libraries who require in-person patron account renewals (so that they can confirm contact information etc.) may also want to send a record of the renewal to their patrons, so it would be nice if the new MEMBERSHIP_RENEWED notice coming with bug 28688 could be sent for manual patron account renewals, not just for automatic account renewals via the membership_expiry.pl cron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 42283] New: Tidy all script tags - cataloguing
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42283 Bug ID: 42283 Summary: Tidy all script tags - cataloguing 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 the assignee for the bug. You are watching all bug changes.

1 44

[Bug 27066] New: Implement Hooks for patron's updates
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27066 Bug ID: 27066 Summary: Implement Hooks for patron's updates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: eric.begin(a)inLibro.com QA Contact: testopia(a)bugs.koha-community.org Some of our clients use external systems to populate Koha's patron information. They can use Koha's API to update patron info, however, we don't have any way (that I know of) to notify an external system when a patron info is changed in Koha. In order to allow bidirectional communications, we are planning to add hooks. This will allow creating plugins to send messages to external systems in order to fulfil the following requirements : - Update patron information stored in the borrowers table (name, address, email, etc.) - Notify an external system when a restriction is placed on a user (fines, manual restrictions, overdues, etc.) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 35

[Bug 39461] New: Cite feature
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39461 Bug ID: 39461 Summary: Cite feature Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Style guide Assignee: oleonard(a)myacpl.org Reporter: lrudikoff(a)massbay.edu QA Contact: martin.renvoize(a)openfifth.co.uk I have a lot of issues with the Cite feature in KOHA (the Cite in Zotero is fine). Personally, I don't like it as it is not correct at all! For example, the entire title of the item is not listed, there is no complete name of the author, and there is no italicizing for citation styles that use it. It also doesn't list which Chicago style it is using. Why is there both a Cite and Cite in Zotero? As a user, I would not scroll down to see the Cite in Zotero and just use the Cite feature which is listed first. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 43869] New: SCO does not honor AllowLinkedAccountHoldPickup
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43869 Bug ID: 43869 Summary: SCO does not honor AllowLinkedAccountHoldPickup Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal 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 Target Milestone: --- To recreate: 1. Enable EnablePatronAccountLinking and WebBasedSelfCheck 2. Set AllowLinkedAccountHoldPickup to 'Allow' and AllowItemsOnHoldCheckoutSCO to 'Don't allow' 3. Have or create 3 patrons for testing. In KTD I use: Patron 1: Edna Patron 2: Henry Patron 3: Ronnie 4. Link Patron 1 and Patron 2 accounts 5. Place a hold for Patron 1 and then check it in to confirm the waiting hold 6. In the staff client check this item out to Patron 2. 7. The checkout actually goes to Patron 1 ( good ) 8. Reset the hold. Put it on hold again for Patron 1, check it in to confirm the waiting hold 9. Log in to self check as Patron 2 and check out the item on hold for Patron 1. 10. The item is checked out to Patron 2 ( wrong ) 11. The item is also still on hold for Patron 1 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 39658] New: Allow definition of non-hierarchical linked patron accounts
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39658 Bug ID: 39658 Summary: Allow definition of non-hierarchical linked patron accounts Change sponsored?: --- 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.m.hall(a)gmail.com In a Koha system containing multiple functionally-autonomous libraries, one patron may have multiple distinct accounts within the same Koha system. These accounts represent distinct cards from distinct libraries and need their circulation rules enforced as such, so they can't be merged into one account. But no one of these accounts is "primary" and they all represent the same person, so guarantor/guarantee relationships are a poor conceptual fit (and may already be in use for their intended purpose). These linked/shared accounts would: - clearly link between each other in the Details of the patron record - optionally reciprocally enforce restrictions and blocks due to fines & fees (when one account is blocked, all are) - optionally allow checkout of on-hold items for shared accounts For that last item, assuming one patron has accounts card1 and card2. They have a hold ready for pickup on their card1 account. If Koha attempts to check the waiting item out to the card2 account, koha should check the item out on the card1 account, mark the hold complete, and give the user a clear on-screen message as to what happened. It should not ask for confirmation. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 169

[Bug 43852] New: When MarkLostItemsAsReturned includes claim_returned and a lost fee is not charged the accountline isn't updated properly
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43852 Bug ID: 43852 Summary: When MarkLostItemsAsReturned includes claim_returned and a lost fee is not charged the accountline isn't updated properly Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- This causes a 500 error if you try to write off the overdue fines for some reason. 1. Set the system preferences: - ClaimReturnedLostValue set to "Claims Return" - ClaimReturnedChargeFee set to "Don't charge a fee" - DefaultLongOverdueSkipLostStatuses not configured - MarkLostItemsAsReturned from the batch item modification tool, from the items tab of the catalog module, from the longoverdue cronjob, when marking an item as a return claim, when receiving payment for the item 2. Have a patron with an item that has become overdue. - The overdue item should have fines. 3. "Claim returned" the overdue item. - Do not charge for the item or make any selections when claiming the item as returned. 4. Go to the patron's account and try to write off the fines. - See the 500 error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 40117] New: Add option for modification of not for loan from items tab
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '26

21 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40117 Bug ID: 40117 Summary: Add option for modification of not for loan from items tab Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Not for loan is a powerful status with a lot of flexibility for libraries, especially since it has the -/+ holdable but not circulating/does not circulate capability. And many libraries are not using it to full advantage because the only way to edit it is from the edit item form, not easily accessible from the items page (moredetail.pl) like other statuses. It would be nice if, perhaps by system preference, a library could optionally make editing of the not for loan status available from moredetail.pl. That way libraries that want NFL status updating a bit more locked down can still only access it from editing an item, and libraries that want staff to be able to use more flexible statuses make it more accessible to staff. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25