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

[Bug 42406] New: Create permission to allow user to delete only their own reports
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42406 Bug ID: 42406 Summary: Create permission to allow user to delete only their own reports 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com It would be helpful to have a permission that allows a user to delete reports they've created themselves but not any report created by another user. The existing permission is "delete_reports" That could be renamed "delete_all_reports" and we could add "delete_own_reports." -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 36

[Bug 38414] New: Can delete reports with only execute_report permission
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38414 Bug ID: 38414 Summary: Can delete reports with only execute_report permission Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org There's a "delete" button within the report preview popup that remains exposed and operable for users with only execute_reports permission. This button should be removed unless one has delete_reports. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 40819] New: Guided reports select column should not be initialized as select2
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40819 Bug ID: 40819 Summary: Guided reports select column should not be initialized as select2 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: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org CC: lisette(a)bywatersolutions.com This is a follow up from bug 37050. To reproduce: 1. Go to Reports > Create guided report 2. Click Next >> 3. Click Next >> 3. Notice the form has been initialized as select2 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 37886] New: SQL reports - Multiselect parameters should be optional
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37886 Bug ID: 37886 Summary: SQL reports - Multiselect parameters should be optional Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: blawlor(a)clamsnet.org Reporter: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 37077 When a report is written with multiselect parameters and the the report is run with nothing selected the report results should not be limited. Multiselect reports use the IN() function, so the SQL should be generated with a comma separated list of all of the authorised values. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37077 [Bug 37077] SQL Reports - Picking only one option for each multiple selection results in wrong query -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 37077] New: SQL Reports - Picking only one option for each multiple selection results in wrong query
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37077 Bug ID: 37077 Summary: SQL Reports - Picking only one option for each multiple selection results in wrong query Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: andrewfh(a)dubcolib.org, blawlor(a)clamsnet.org, caroline.cyr-la-rose(a)inlibro.com Depends on: 35746 To reproduce: 1. Go to Reports and create a report from SQL select * from items where homebranch in <<Libraries|branches:in>> and itype in <<Item type|itemtypes:in>> 3. Run the report but pick only 1 library and 1 item type 4. Click the "Show SQL code" 5. Notice itype value is wrong. It's using the same value selected for library. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35746 [Bug 35746] Multiple selections for parameters used in the IN function -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 39569] New: When cancelling a hold waiting past expiration date triggers a transfer the libraries name is not in alert
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39569 Bug ID: 39569 Summary: When cancelling a hold waiting past expiration date triggers a transfer the libraries name is not in alert 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: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To recreate: - Use a bib with a single item to make this easier - Place two holds on a bib with pickup at one library - Place some more holds for pickup at a different library - Check the item in to the first library - Set the expiration date back in time, using ktd --dbshell can help update reserves set expirationdate = DATE('2024-01-01') where branchcode='CPL'; - On Holds awaiting pickup > Holds waiting past their expiration date use the button in the actions tab to 'Cancel hold' the alert says: This item is on hold for pick-up at your library' - click OK - Check the item in again and set expiration date to expired again - On Holds awaiting pickup > Holds waiting past their expiration date use the button in the actions tab to 'Cancel hold and transfer to: [libraryname]' - Notice the alert says 'This item is on hold for pick-up at' with no library name -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 39597] New: When cancelling multiple holds on a bib record cancel_hold_alert has very low contrast
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39597 Bug ID: 39597 Summary: When cancelling multiple holds on a bib record cancel_hold_alert has very low contrast Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: blawlor(a)clamsnet.org QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org Created attachment 180747 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=180747&action=e… screnshot To recreate: - Go to a bib record and place multiple holds on it - Select multiple holds and click 'Cancel selected (4)' - The Alert says 'This action will cancel 4 hold(s).' - Note that the contrast on the number of holds is very low -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 43389] Remove conditional TT tags from tables thead (Holdings tables)
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43389 --- Comment #2 from Owen Leonard <oleonard(a)myacpl.org> --- Created attachment 204591 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=204591&action=e… Bug 43389: Remove conditional TT tags from holdings table thead The item tables are built with TT's IFs conditions inside their `thead`, changing the number of rendered columns depending on system preferences and permissions. This is the pattern already fixed by bug 42332. Column visibility is now driven by the existing table_settings 'visibility_condition' mechanism. A 'create_analytics' column was added to admin/columns_settings.yml for the "Create analytics" header Test plan: On a bibliographic record with items (catalogue/detail.pl), toggle each of these system preferences one at a time and reload the page: LocalCoverImages, EnableItemGroups, EasyAnalyticalRecords, UseCourseReserves. Confirm the matching column appears/disappears in both the "Holdings" and "Other holdings" tabs, with no JS errors in the console. Signed-off-by: Owen Leonard <oleonard(a)myacpl.org> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 43389] Remove conditional TT tags from tables thead (Holdings tables)
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43389 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #204265|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 43389] Remove conditional TT tags from tables thead (Holdings tables)
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=43389 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Patch complexity|--- |Small patch Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0