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

[Bug 38384] New: General fix for plugins breaking database transactions
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '26

30 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38384 Bug ID: 38384 Summary: General fix for plugins breaking database transactions 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: philip.orr(a)lmscloud.de QA Contact: testopia(a)bugs.koha-community.org In Bug 36736, a call to get_enabled_plugins was added to background jobs to ensure plugins wouldn't break the database transaction. We need a fix for this problem in general (Database transactions breaking due to plugin hooks being called), not just for background jobs. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 108

[Bug 20732] New: Display the note tab for records without items.
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '26

30 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20732 Bug ID: 20732 Summary: Display the note tab for records without items. Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: patrick.robitaille(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, when we have a record who have no items, it would be great to displays the note tab first instead of holdings. It would be useful for the records of electronic resources who don't have items. Having the notes tab put forward would avoid one more click for relevant information. It could be a system preference like opacSerialDefaultTab but for the records without items. Thanks, Patrick. -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 38776] New: Propose a list of value for restriction comment
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '26

30 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38776 Bug ID: 38776 Summary: Propose a list of value for restriction comment 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: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be nice to let librarians use one of several pre-filled values in the restriction comment for a manual restrictions. The values could be provided by authorised value with category "R_COMMENTS". Values could be selected although another comment could be hand-typed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 41

[Bug 33312] New: Add circulation and fines rules table from smart-rules.pl to column settings
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '26

30 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33312 Bug ID: 33312 Summary: Add circulation and fines rules table from smart-rules.pl to column settings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be very helpful to be able to configure hiding columns as libraries rarely (if ever) use all the columns (suspensions vs fines, etc.) Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 38822] New: View easilty the months for which usage reports have been collected for a given source
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '26

29 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38822 Bug ID: 38822 Summary: View easilty the months for which usage reports have been collected for a given source Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com It could be nice to make it easy to view the months for which various usage reports have been collected for a given source (without the need to create a report in Koha) (FOLIO ERM or Coral could be source of inspiration) -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 37328] New: Cannot delete report after using Update and Run SQL button
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '26

29 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37328 Bug ID: 37328 Summary: Cannot delete report after using Update and Run SQL button Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org To recreate: - create a report or edit an existing one - on the edit screen (/cgi-bin/koha/reports/guided_reports.pl?id=XXX&op=edit_form), click "Update and run SQL" - On the resulting page, where you see both your results and the edit form, click Edit and then Delete - Nothing happens. The delete confirm modal doesn't appear, so the deletion doesn't move forward. The url on that results + edit screen is just "/cgi-bin/koha/reports/guided_reports.pl" -- I don't know if that's part of the issue? The report can still be deleted from other pages. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 37206] New: Removing an item from a label batch should be a CSRF-protected POST operation
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '26

29 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37206 Bug ID: 37206 Summary: Removing an item from a label batch should be a CSRF-protected POST operation Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 36192 >From Labels -> Manage label batches -> Edit batch, the list of items in the batch has a "Delete" button for each item. Currently it's a GET operation sent via a link, but I think that should be POSTed. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36192 [Bug 36192] [OMNIBUS] CSRF Protection for Koha -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 30657] New: Make patron attributes available via Template Toolkit in overdues
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '26

29 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30657 Bug ID: 30657 Summary: Make patron attributes available via Template Toolkit in overdues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When using Template Toolkit to fetch patron values, one should be able to fetch patron attribute values. This would be useful both for printing those values into the notice content and for using those values in logic to vary the notices per patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 100

[Bug 25408] New: CanBookBeReserved should check "opacitemholds" policy
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '26

29 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25408 Bug ID: 25408 Summary: CanBookBeReserved should check "opacitemholds" policy Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com how to reproduce : Set an issuing rule with opacitemholds set to "Force" Make a search and select multiple records Place a hold on those records (using multi-hold records) Verify hold is placed on the record (next item available) where it shouldn't! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 161

[Bug 38228] New: Allow libraries to choose which auto renewal errors to report on in auto renew notices
by bugzilla-daemon＠bugs.koha-community.org 29 Oct '26

29 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38228 Bug ID: 38228 Summary: Allow libraries to choose which auto renewal errors to report on in auto renew notices 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 Automatic renewal notices can report will report on many errors like 'on_reserve', 'restriction' , 'overdue' , 'auto_too_late' , 'auto_too_much_oweing' , 'too_unseen', 'too_many', etc. You can control which errors are reported on via TT in the notice. It would be nice if their was a simpler way ( system preference ) where libraries could chose which errors get reported on and which are skipped. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1