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

[Bug 33728] New: Add a way to copy a report result to clipboard
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33728 Bug ID: 33728 Summary: Add a way to copy a report result to clipboard Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org It could be useful to have a button or a menu to copy easily the result of a report to clipboard -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 39394] New: Client-side conversion of CSV to Excel and ODS formats
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39394 Bug ID: 39394 Summary: Client-side conversion of CSV to Excel and ODS formats Change sponsored?: --- 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: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Since ODS generation can cause issues (https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23685) and Excel generation is not currently possible, why not using libraries such as https://sheetjs.com/ (and other tools like https://www.papaparse.com/ or web workers for big files?) to convert the generated CSV to Excel or ODS in the browser ? It could be used for reports but also other CSV generated by Koha. We will try this approach in my library, as a local customization. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 41090] New: Final auto renewal error not handled in renew.pl
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41090 Bug ID: 41090 Summary: Final auto renewal error not handled in renew.pl 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com To recreate: 1 - Set a circ rule for: Renewals Allowed: 1 Renewal period: 5 No renewal before: 6 No automatic renewal before: 6 Auto renewal: Yes 2 - Issue an item that matches that rule 3 - Use the 'Renew' tab in the toolbar or browse to Circulation->Renew 4 - Enter the item barcode 5 - You see 2 messages: Cannot renew: auto_renew_final "Continue without renewing" Item renewed.. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 40237] New: Update reserves/request.pl to use Koha::Patron->can_place_holds
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40237 Bug ID: 40237 Summary: Update reserves/request.pl to use Koha::Patron->can_place_holds Change sponsored?: --- 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: martin.renvoize(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org Depends on: 40101 Bug 40101 adds the new 'can_place_holds' method to Koha::Patron, but it avoided updating this complex controller and template to utilise it. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40101 [Bug 40101] Add `Koha::Patron->can_place_holds` -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 39204] New: Problem with cancelling a hold via SIP without marking it as waiting returns an error
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39204 Bug ID: 39204 Summary: Problem with cancelling a hold via SIP without marking it as waiting returns an error Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org >From Bug 38615: "When testing I noticed something both with and without the patch (so this is a general SIP question) If you place a hold and then try to cancel the hold with this command before checking the item into the hold shelf the SIP cancel request returns |AFError with transaction drop_hold:|" Easy to recreate with SIP emulator: 1. /kohadevbox/koha/misc/sip_cli_emulator.pl -a localhost -p 6001 -l CPL -su term1 -sp term1 -m hold --patron 23529000035676 --item 39999000001310 --hold-mode + 2. /kohadevbox/koha/misc/sip_cli_emulator.pl -a localhost -p 6001 -l CPL -su term1 -sp term1 -m hold --patron 23529000035676 --item 39999000001310 --hold-mode - 3. See the error: AFError with transaction drop_hold: -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 28491] New: field 003 not updated after import
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28491 Bug ID: 28491 Summary: field 003 not updated after import Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org I import some authority data from e.g. dnb.de, which contains: <controlfield tag="001">11915725X</controlfield> <controlfield tag="003">DE-101</controlfield> After the import, the local authority data looks like <controlfield tag="001">35</controlfield> <controlfield tag="003">DE-101</controlfield> So 001 now contains the internal Koha id (good), but 003 still points to DE-101 (i.e. dnb.de), which I think is bad, because if I look up the ID '35' in the linked DB DE-101, I will now get a bad result. I assume that 003 should be set to my MARCOrgCode Looking at the code, I find (in C4::AuthoritiesMarc, AddAuthority, 568ff) if (!$record->field('003')) { $record->insert_fields_ordered( MARC::Field->new('003', $marcorgcode), ); } So this behavior seems intentional? If so, I still find it very unlogical and buggy. I assume that both 001 and 003 should be overwritten with data pointing to the current Koha instance, and the original 001/003 "archived" in 035 and/or 040 I could easily provide a patch that changes this behavior, but I'm not sure if this would cause confusion / failing tests / etc. Maybe add an option to allow a force-overwrite of 003? Greeting, Thomas PS this seems slightly related to #25603 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 40

[Bug 40701] New: Message "Checkouts are BLOCKED because fine balance is OVER THE LIMIT." doesn't display anymore
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40701 Bug ID: 40701 Summary: Message "Checkouts are BLOCKED because fine balance is OVER THE LIMIT." doesn't display anymore Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I was trying to get the message "Checkouts are BLOCKED because fine balance is OVER THE LIMIT." to appear in main because I wanted to change it to "charge balance" or simply "balance" instead of "fine balance" (I got a comment from a confused client on 24.05 whose library doesn't charge fines...). It seems, this message doesn't appear anymore in main? It's still in the .inc though. To recreate: 1. Go to a patron account > Accounting > Create manual invoice 2. Add a Manual fee charge of 100 and click Save 3. Go to Details --> There is a message about the fee, but it doesn't say "Checkouts are BLOCKED because fine balance is OVER THE LIMIT." 4. Go to Checkouts -- Same. I feel like it's an unintended change in behaviour brought by bug 28924, maybe? The IF right above the message was changed and I think that's what prevents the message from displaying, but I'm not sure enough to fix it myself. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 37532] New: Protected status should have a permission to block editing patron
by bugzilla-daemon＠bugs.koha-community.org 10 Apr '26

10 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37532 Bug ID: 37532 Summary: Protected status should have a permission to block editing patron Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, protected status prevents accidental deletion of a patron account. With bug 36085, an extra layer will be added to protect that status from being turned on or off with a permission. However, the account is not fully protected, as important information can be altered in the account by editing it. I would like to see an option for protected status, that would allow us to decide if this protected status will also prevent others from editing the account at all, unless they have the permission in bug 36085. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 40183] New: Record diff in action logs when editing notices
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40183 Bug ID: 40183 Summary: Record diff in action logs when editing notices Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 37940 Notices would be a good place to implement the diff column for action logs. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37940 [Bug 37940] [OMNIBUS] All modification logged via action logs should include original to create JSON diff -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 38296] New: Investigate DataTables's extension StateRestore
by bugzilla-daemon＠bugs.koha-community.org 09 Apr '26

09 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38296 Bug ID: 38296 Summary: Investigate DataTables's extension StateRestore Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 33484, 36640 https://datatables.net/extensions/staterestore/index#Features Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33484 [Bug 33484] Ability to remember user's selected table configuration and search filters for tables https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36640 [Bug 36640] Upgrade DataTables from 1.13.6 to 2.x -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4