https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Michelle Spinney <mspinney@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mspinney@clamsnet.org -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #1 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200213 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200213&action=edit Bug 42621: Add a ft_reports column to library_groups Patch from commit a283fa7 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #3 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200215 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200215&action=edit Bug 42621: Handle the new ft_reports column in the UI Patch from commit 4ae0505 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #5 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200217 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200217&action=edit Bug 42621: Update reports search to be able to look up by library group Patch from commit 7e47801 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #7 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200219 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200219&action=edit Bug 42621: Add unit test for lib group limits Test plan: Prerequisites 1. Three branches: Centerville, Fairfield, Fairview 2. Admin - Library groups: create root group "Test Group", enable Limit report access by group, add Centerville and Fairfield as child libraries (not Fairview) 3. Create an admin user with manage_report_limits permission (or superlibrarian) at branch Centerville 4. Create regular users with reports + execute_reports only (no manage_report_limits), one at each of Centerville, Fairfield, and Fairview 5. Admin - Administration - Columns settings - Reports - Saved reports (table_reports) - enable the Library limits column (it is hidden by default) Baseline - LimitReportsBy = No restriction 6. Set LimitReportsBy = No restriction 7. Admin user - create Report A - no "Library limitation" field visible, save report with any parameters, content is not important 8. Admin user - Reports list - no "Library limits" column visible even if enabled in column settings. Library mode - regression 9. Set LimitReportsBy = Library 10. Admin user - Reports list - "Library limits" column visible (if enabled in column settings) 11. Log in as the Fairview user - Reports list - "Library limits" column not visible as user doesn’t have manage_reports_limit permission 12. Admin user - edit Report A - Library limitation field should be visible - set limit to Centerville - report saves with Centerville limit 13. Fairview user - Reports list - Report A not visible 14. Regular user at Centerville - Reports list - Report A visible 15. Regular user at Centerville - edit Report A - save - limits preserved (fieldset not shown; backend preserves existing limits silently) 16. Admin user - Report A visible with "1 library limitation" tooltip showing Centerville. Delete Report A Library group mode - setup and limits column 17. Set LimitReportsBy = library_group 18. Admin user - Reports list - "Library limits" column still visible 19. Regular user at Centerville - Reports list - "Library limits" column not visible 20. Admin user - create Report B, set limit to Centerville - "Library limitation" fieldset visible, saves with Centerville as the limit 21. Admin user - Reports list - Report B shows "Test Group" in limits column 22. Admin user - create Report C with no limit - Report C shows "No limitation" in limits column Library group mode - access by group membership 23. Fairfield user - Reports list - Report B visible (Fairfield is in the same group as Centerville). Report C also visible (no limitation) 24. Fairview user - Reports list - Report B not visible (Fairview not in group) 25. Fairview user - navigate directly to Report B URL - access denied 26. Fairview user - Reports list - Report C visible (no limitation) Library group mode - ft_reports flag required 27. Admin - Library groups: disable "Limit report access by group" on "Test Group" 28. Regular user at Fairfield - Reports list - Report B no longer visible as it was limited to Centerville 29. Admin user - Report B limits column - shows "No limitation" 30. Re-enable the flag - Fairfield can see Report B again Library group mode - non-admin save behaviour 31. Regular user at Centerville - create new Report D - save - Report D automatically limited to Centerville (backend sets own branch; no fieldset shown). Verify by viewing the saved reports table as the Admin user - should show Test group as the limitation 32. Regular user at Centerville - edit Report B - save - existing limits preserved unchanged Switching modes 33. With Report B limited to Centerville and LimitReportsBy = library_group - Fairfield can access 34. Switch to LimitReportsBy to Library - Fairfield can no longer access Report B (exact branch match only) 35. Switch back to library_group - Fairfield can access Report B again 36. Switch to none - all reports accessible; no limits column or fieldset anywhere -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |matt.blenkinsop@openfifth.c |ity.org |o.uk CC| |matt.blenkinsop@openfifth.c | |o.uk -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200214|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200216|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200218|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200220|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #10 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200235 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200235&action=edit Bug 42621: Update the LimitReportsByLibrary to LimitReportsBy Patch from commit 40da003 -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #12 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200237 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200237&action=edit Bug 42621: Add library group limit classes Designed to work as an extra layer on top of library_limits by using the same column but expanding the search to also include any branches in a library group -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #14 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200239 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200239&action=edit Bug 42621: Update logic involving the old syspref to reflect the new LimitReportsBy Patch from commit 1ce739d -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #16 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200241 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200241&action=edit Bug 42621: DBIC Patch from commit c0c2150 -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA CC| |blawlor@clamsnet.org --- Comment #17 from Brendan Lawlor <blawlor@clamsnet.org> --- This works quite nicely as described. I'm only failing QA because the qa script picks up a tidy issue: [FAIL] t/db_dependent/Koha/Reports.t FAIL tidiness File is not tidy, please run `perl misc/devel/tidy.pl t/db_dependent/Koha/Reports.t` Also, I'm not sure if this is an issue with the atomic update, but if you run updatedatabase twice you get an error: DEV atomic update /kohadevbox/koha/installer/data/mysql/atomicupdate/bug_42621.pl [19:29:08]: Bug 42621 - Extend report limitations by library to use library groups ERROR: {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry 'LimitReportsBy' for key 'PRIMARY' at /kohadevbox/koha/C4/Installer.pm line 818 Other than that this is looking good. Nice work! -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200234|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200236|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200238|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200240|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #18 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200424 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200424&action=edit Bug 42621: Add a ft_reports column to library_groups Patch from commit 66e0762 -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #20 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200426 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200426&action=edit Bug 42621: Handle the new ft_reports column in the UI Patch from commit 2968c35 -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #22 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200428 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200428&action=edit Bug 42621: Update reports search to be able to look up by library group Patch from commit e83e6fa -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #24 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 200430 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200430&action=edit Bug 42621: Add unit test for lib group limits Test plan: Prerequisites 1. Three branches: Centerville, Fairfield, Fairview 2. Admin - Library groups: create root group "Test Group", enable Limit report access by group, add Centerville and Fairfield as child libraries (not Fairview) 3. Create an admin user with manage_report_limits permission (or superlibrarian) at branch Centerville 4. Create regular users with reports + execute_reports only (no manage_report_limits), one at each of Centerville, Fairfield, and Fairview 5. Admin - Administration - Columns settings - Reports - Saved reports (table_reports) - enable the Library limits column (it is hidden by default) Baseline - LimitReportsBy = No restriction 6. Set LimitReportsBy = No restriction 7. Admin user - create Report A - no "Library limitation" field visible, save report with any parameters, content is not important 8. Admin user - Reports list - no "Library limits" column visible even if enabled in column settings. Library mode - regression 9. Set LimitReportsBy = Library 10. Admin user - Reports list - "Library limits" column visible (if enabled in column settings) 11. Log in as the Fairview user - Reports list - "Library limits" column not visible as user doesn’t have manage_reports_limit permission 12. Admin user - edit Report A - Library limitation field should be visible - set limit to Centerville - report saves with Centerville limit 13. Fairview user - Reports list - Report A not visible 14. Regular user at Centerville - Reports list - Report A visible 15. Regular user at Centerville - edit Report A - save - limits preserved (fieldset not shown; backend preserves existing limits silently) 16. Admin user - Report A visible with "1 library limitation" tooltip showing Centerville. Delete Report A Library group mode - setup and limits column 17. Set LimitReportsBy = library_group 18. Admin user - Reports list - "Library limits" column still visible 19. Regular user at Centerville - Reports list - "Library limits" column not visible 20. Admin user - create Report B, set limit to Centerville - "Library limitation" fieldset visible, saves with Centerville as the limit 21. Admin user - Reports list - Report B shows "Test Group" in limits column 22. Admin user - create Report C with no limit - Report C shows "No limitation" in limits column Library group mode - access by group membership 23. Fairfield user - Reports list - Report B visible (Fairfield is in the same group as Centerville). Report C also visible (no limitation) 24. Fairview user - Reports list - Report B not visible (Fairview not in group) 25. Fairview user - navigate directly to Report B URL - access denied 26. Fairview user - Reports list - Report C visible (no limitation) Library group mode - ft_reports flag required 27. Admin - Library groups: disable "Limit report access by group" on "Test Group" 28. Regular user at Fairfield - Reports list - Report B no longer visible as it was limited to Centerville 29. Admin user - Report B limits column - shows "No limitation" 30. Re-enable the flag - Fairfield can see Report B again Library group mode - non-admin save behaviour 31. Regular user at Centerville - create new Report D - save - Report D automatically limited to Centerville (backend sets own branch; no fieldset shown). Verify by viewing the saved reports table as the Admin user - should show Test group as the limitation 32. Regular user at Centerville - edit Report B - save - existing limits preserved unchanged Switching modes 33. With Report B limited to Centerville and LimitReportsBy = library_group - Fairfield can access 34. Switch to LimitReportsBy to Library - Fairfield can no longer access Report B (exact branch match only) 35. Switch back to library_group - Fairfield can access Report B again 36. Switch to none - all reports accessible; no limits column or fieldset anywhere -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Brendan Lawlor <blawlor@clamsnet.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Sponsorship status|--- |Sponsored Comma delimited| |CLAMS list of Sponsors| | Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #26 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 200462 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200462&action=edit Bug 42621: Add a ft_reports column to library_groups Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #28 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 200464 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200464&action=edit Bug 42621: Handle the new ft_reports column in the UI Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #30 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 200466 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200466&action=edit Bug 42621: Update reports search to be able to look up by library group Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #32 from Brendan Lawlor <blawlor@clamsnet.org> --- Created attachment 200468 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=200468&action=edit Bug 42621: Add unit test for lib group limits Test plan: Prerequisites 1. Three branches: Centerville, Fairfield, Fairview 2. Admin - Library groups: create root group "Test Group", enable Limit report access by group, add Centerville and Fairfield as child libraries (not Fairview) 3. Create an admin user with manage_report_limits permission (or superlibrarian) at branch Centerville 4. Create regular users with reports + execute_reports only (no manage_report_limits), one at each of Centerville, Fairfield, and Fairview 5. Admin - Administration - Columns settings - Reports - Saved reports (table_reports) - enable the Library limits column (it is hidden by default) Baseline - LimitReportsBy = No restriction 6. Set LimitReportsBy = No restriction 7. Admin user - create Report A - no "Library limitation" field visible, save report with any parameters, content is not important 8. Admin user - Reports list - no "Library limits" column visible even if enabled in column settings. Library mode - regression 9. Set LimitReportsBy = Library 10. Admin user - Reports list - "Library limits" column visible (if enabled in column settings) 11. Log in as the Fairview user - Reports list - "Library limits" column not visible as user doesn’t have manage_reports_limit permission 12. Admin user - edit Report A - Library limitation field should be visible - set limit to Centerville - report saves with Centerville limit 13. Fairview user - Reports list - Report A not visible 14. Regular user at Centerville - Reports list - Report A visible 15. Regular user at Centerville - edit Report A - save - limits preserved (fieldset not shown; backend preserves existing limits silently) 16. Admin user - Report A visible with "1 library limitation" tooltip showing Centerville. Delete Report A Library group mode - setup and limits column 17. Set LimitReportsBy = library_group 18. Admin user - Reports list - "Library limits" column still visible 19. Regular user at Centerville - Reports list - "Library limits" column not visible 20. Admin user - create Report B, set limit to Centerville - "Library limitation" fieldset visible, saves with Centerville as the limit 21. Admin user - Reports list - Report B shows "Test Group" in limits column 22. Admin user - create Report C with no limit - Report C shows "No limitation" in limits column Library group mode - access by group membership 23. Fairfield user - Reports list - Report B visible (Fairfield is in the same group as Centerville). Report C also visible (no limitation) 24. Fairview user - Reports list - Report B not visible (Fairview not in group) 25. Fairview user - navigate directly to Report B URL - access denied 26. Fairview user - Reports list - Report C visible (no limitation) Library group mode - ft_reports flag required 27. Admin - Library groups: disable "Limit report access by group" on "Test Group" 28. Regular user at Fairfield - Reports list - Report B no longer visible as it was limited to Centerville 29. Admin user - Report B limits column - shows "No limitation" 30. Re-enable the flag - Fairfield can see Report B again Library group mode - non-admin save behaviour 31. Regular user at Centerville - create new Report D - save - Report D automatically limited to Centerville (backend sets own branch; no fieldset shown). Verify by viewing the saved reports table as the Admin user - should show Test group as the limitation 32. Regular user at Centerville - edit Report B - save - existing limits preserved unchanged Switching modes 33. With Report B limited to Centerville and LimitReportsBy = library_group - Fairfield can access 34. Switch to LimitReportsBy to Library - Fairfield can no longer access Report B (exact branch match only) 35. Switch back to library_group - Fairfield can access Report B again 36. Switch to none - all reports accessible; no limits column or fieldset anywhere Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #34 from Brendan Lawlor <blawlor@clamsnet.org> --- This works as described and is a big improvement for consortia that need to manage a lot of reports. For example some reports only need to be used by system administrators, and this will allow us to display only relevant reports to the right people. Just noting here the qa script flags one other issue: [FAIL] C4/Reports/Guided.pm FAIL pod_coverage sub _build_query has no pod coverage. sub _get_columns has no pod coverage. sub _get_display_value has no pod coverage. But that is an issue before the patch too. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200462|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200464|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200466|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #200468|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #36 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 206094 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206094&action=edit Bug 42621: Add a ft_reports column to library_groups Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #38 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 206096 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206096&action=edit Bug 42621: Handle the new ft_reports column in the UI Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #40 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 206098 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206098&action=edit Bug 42621: Update reports search to be able to look up by library group Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #42 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 206100 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206100&action=edit Bug 42621: Add unit test for lib group limits Test plan: Prerequisites 1. Three branches: Centerville, Fairfield, Fairview 2. Admin - Library groups: create root group "Test Group", enable Limit report access by group, add Centerville and Fairfield as child libraries (not Fairview) 3. Create an admin user with manage_report_limits permission (or superlibrarian) at branch Centerville 4. Create regular users with reports + execute_reports only (no manage_report_limits), one at each of Centerville, Fairfield, and Fairview 5. Admin - Administration - Columns settings - Reports - Saved reports (table_reports) - enable the Library limits column (it is hidden by default) Baseline - LimitReportsBy = No restriction 6. Set LimitReportsBy = No restriction 7. Admin user - create Report A - no "Library limitation" field visible, save report with any parameters, content is not important 8. Admin user - Reports list - no "Library limits" column visible even if enabled in column settings. Library mode - regression 9. Set LimitReportsBy = Library 10. Admin user - Reports list - "Library limits" column visible (if enabled in column settings) 11. Log in as the Fairview user - Reports list - "Library limits" column not visible as user doesn’t have manage_reports_limit permission 12. Admin user - edit Report A - Library limitation field should be visible - set limit to Centerville - report saves with Centerville limit 13. Fairview user - Reports list - Report A not visible 14. Regular user at Centerville - Reports list - Report A visible 15. Regular user at Centerville - edit Report A - save - limits preserved (fieldset not shown; backend preserves existing limits silently) 16. Admin user - Report A visible with "1 library limitation" tooltip showing Centerville. Delete Report A Library group mode - setup and limits column 17. Set LimitReportsBy = library_group 18. Admin user - Reports list - "Library limits" column still visible 19. Regular user at Centerville - Reports list - "Library limits" column not visible 20. Admin user - create Report B, set limit to Centerville - "Library limitation" fieldset visible, saves with Centerville as the limit 21. Admin user - Reports list - Report B shows "Test Group" in limits column 22. Admin user - create Report C with no limit - Report C shows "No limitation" in limits column Library group mode - access by group membership 23. Fairfield user - Reports list - Report B visible (Fairfield is in the same group as Centerville). Report C also visible (no limitation) 24. Fairview user - Reports list - Report B not visible (Fairview not in group) 25. Fairview user - navigate directly to Report B URL - access denied 26. Fairview user - Reports list - Report C visible (no limitation) Library group mode - ft_reports flag required 27. Admin - Library groups: disable "Limit report access by group" on "Test Group" 28. Regular user at Fairfield - Reports list - Report B no longer visible as it was limited to Centerville 29. Admin user - Report B limits column - shows "No limitation" 30. Re-enable the flag - Fairfield can see Report B again Library group mode - non-admin save behaviour 31. Regular user at Centerville - create new Report D - save - Report D automatically limited to Centerville (backend sets own branch; no fieldset shown). Verify by viewing the saved reports table as the Admin user - should show Test group as the limitation 32. Regular user at Centerville - edit Report B - save - existing limits preserved unchanged Switching modes 33. With Report B limited to Centerville and LimitReportsBy = library_group - Fairfield can access 34. Switch to LimitReportsBy to Library - Fairfield can no longer access Report B (exact branch match only) 35. Switch back to library_group - Fairfield can access Report B again 36. Switch to none - all reports accessible; no limits column or fieldset anywhere Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #44 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- When LimitReportsBy is set to "Group," limiting a report to a library that is not in a group with "Limit report access by group" selected results in a limit to a single branch that is enforced but not displayed. To recreate: - be logged in as a superlibrarian at Centerville - set LimitReportsBy to Group - create a library group containing Centerville and Fairfield, set it to "Limit report access by group" - create a new report, set a branch limit to Fairview - confirm your new report does not show in your Saved Reports list - still as your superlibrarian, set your library to Fairview - confirm you can now see your report in the Saved Reports list, but it shows "No limitation" It is correct to enforce a limit to an ungrouped library (effectively treating a library that is not in a reports limit group as being in its own group of 1). We should show that limitation to users. Other than this, test plan checks out and unit tests all pass. Looking good! -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #46 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 206264 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206264&action=edit Bug 42621: (QA follow-up) Display and enforce limits to ungrouped libraries When LimitReportsBy is set to library_group and a report is limited to a library that is not in any group with "Limit report access by group" enabled, the limit was enforced in the saved reports list but the "Library limits" column showed "No limitation". Direct access via can_access also ignored the limit entirely, because it only checked qualifying groups. An ungrouped library is now treated as a group of one. Two helpers are added to Koha::Object::Limit::LibraryGroup: - ungrouped_library_limits returns the limited libraries that are not members of any qualifying group - library_group_limit_branchcodes returns every branchcode the limit resolves to (stored branchcodes plus all members of qualifying groups) can_access uses the resolved branchcodes so listing and direct access agree. The saved reports table shows group titles followed by any ungrouped libraries as "Branch name (CODE)". Test plan: 1. Set LimitReportsBy to Library group 2. Create a library group containing Centerville and Fairfield, tick "Limit report access by group" 3. As a superlibrarian at Centerville, create a report limited to Fairview (not in any group) 4. Saved reports list: the report is hidden 5. Set your library to Fairview, reload the saved reports list 6. The report is visible and the Library limits column shows "Fairview (FRV)" instead of "No limitation" 7. Edit the report and add Centerville to the limit. The column shows the group title followed by "Fairview (FRV)" 8. Log in as a non-manager user at Fairfield and open the report from step 3 by URL. Access is denied 9. prove t/db_dependent/Koha/Reports.t Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #49 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- The Library Limits column is showing if LimitReportsBy is set to "library" or "library group" and when set to "group" I correctly see a mix of groups and ungrouped libraries. When LimitReportsBy is set to "Library" or "Library group" then the saved reports table doesn't include the standard DataTables stuff: pagination controls, search filter, Columns, Export, etc. When LimitReportsBy is set to "Library" and a report is limited, the Library Limits column shows "X Library Limitation(s)" and one can mouse over to see the list of libraries in a tooltip. But if it's set to "Library group" then the column lists the groups and ungrouped libraries directly, rather than in a tooltip. Can these be made consistent? -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #206095|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #206097|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #206099|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #206101|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #206265|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #51 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 206628 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206628&action=edit Bug 42621: Update the LimitReportsByLibrary to LimitReportsBy Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #53 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 206630 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206630&action=edit Bug 42621: Add library group limit classes Designed to work as an extra layer on top of library_limits by using the same column but expanding the search to also include any branches in a library group Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #55 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 206632 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206632&action=edit Bug 42621: Update logic involving the old syspref to reflect the new LimitReportsBy Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #57 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 206634 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206634&action=edit Bug 42621: DBIC Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #59 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 206636 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206636&action=edit Bug 42621: (QA follow-up) Add POD to private subs in C4::Reports::Guided The QA script reports missing POD coverage for _get_columns, _build_query and _get_display_value. This is pre-existing but was requested during QA of this bug. Test plan: 1. prove t/db_dependent/Reports/Guided.t 2. Run the QA script, C4/Reports/Guided.pm no longer fails pod_coverage Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #61 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 206687 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206687&action=edit Bug 42621: Add a ft_reports column to library_groups Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #63 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 206689 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206689&action=edit Bug 42621: Handle the new ft_reports column in the UI Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #65 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 206691 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206691&action=edit Bug 42621: Update reports search to be able to look up by library group Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #67 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 206693 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206693&action=edit Bug 42621: Add unit test for lib group limits Test plan: Prerequisites 1. Three branches: Centerville, Fairfield, Fairview 2. Admin - Library groups: create root group "Test Group", enable Limit report access by group, add Centerville and Fairfield as child libraries (not Fairview) 3. Create an admin user with manage_report_limits permission (or superlibrarian) at branch Centerville 4. Create regular users with reports + execute_reports only (no manage_report_limits), one at each of Centerville, Fairfield, and Fairview 5. Admin - Administration - Columns settings - Reports - Saved reports (table_reports) - enable the Library limits column (it is hidden by default) Baseline - LimitReportsBy = No restriction 6. Set LimitReportsBy = No restriction 7. Admin user - create Report A - no "Library limitation" field visible, save report with any parameters, content is not important 8. Admin user - Reports list - no "Library limits" column visible even if enabled in column settings. Library mode - regression 9. Set LimitReportsBy = Library 10. Admin user - Reports list - "Library limits" column visible (if enabled in column settings) 11. Log in as the Fairview user - Reports list - "Library limits" column not visible as user doesn’t have manage_reports_limit permission 12. Admin user - edit Report A - Library limitation field should be visible - set limit to Centerville - report saves with Centerville limit 13. Fairview user - Reports list - Report A not visible 14. Regular user at Centerville - Reports list - Report A visible 15. Regular user at Centerville - edit Report A - save - limits preserved (fieldset not shown; backend preserves existing limits silently) 16. Admin user - Report A visible with "1 library limitation" tooltip showing Centerville. Delete Report A Library group mode - setup and limits column 17. Set LimitReportsBy = library_group 18. Admin user - Reports list - "Library limits" column still visible 19. Regular user at Centerville - Reports list - "Library limits" column not visible 20. Admin user - create Report B, set limit to Centerville - "Library limitation" fieldset visible, saves with Centerville as the limit 21. Admin user - Reports list - Report B shows "Test Group" in limits column 22. Admin user - create Report C with no limit - Report C shows "No limitation" in limits column Library group mode - access by group membership 23. Fairfield user - Reports list - Report B visible (Fairfield is in the same group as Centerville). Report C also visible (no limitation) 24. Fairview user - Reports list - Report B not visible (Fairview not in group) 25. Fairview user - navigate directly to Report B URL - access denied 26. Fairview user - Reports list - Report C visible (no limitation) Library group mode - ft_reports flag required 27. Admin - Library groups: disable "Limit report access by group" on "Test Group" 28. Regular user at Fairfield - Reports list - Report B no longer visible as it was limited to Centerville 29. Admin user - Report B limits column - shows "No limitation" 30. Re-enable the flag - Fairfield can see Report B again Library group mode - non-admin save behaviour 31. Regular user at Centerville - create new Report D - save - Report D automatically limited to Centerville (backend sets own branch; no fieldset shown). Verify by viewing the saved reports table as the Admin user - should show Test group as the limitation 32. Regular user at Centerville - edit Report B - save - existing limits preserved unchanged Switching modes 33. With Report B limited to Centerville and LimitReportsBy = library_group - Fairfield can access 34. Switch to LimitReportsBy to Library - Fairfield can no longer access Report B (exact branch match only) 35. Switch back to library_group - Fairfield can access Report B again 36. Switch to none - all reports accessible; no limits column or fieldset anywhere Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #69 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 206695 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206695&action=edit Bug 42621: (QA follow-up) Display and enforce limits to ungrouped libraries When LimitReportsBy is set to library_group and a report is limited to a library that is not in any group with "Limit report access by group" enabled, the limit was enforced in the saved reports list but the "Library limits" column showed "No limitation". Direct access via can_access also ignored the limit entirely, because it only checked qualifying groups. An ungrouped library is now treated as a group of one. Two helpers are added to Koha::Object::Limit::LibraryGroup: - ungrouped_library_limits returns the limited libraries that are not members of any qualifying group - library_group_limit_branchcodes returns every branchcode the limit resolves to (stored branchcodes plus all members of qualifying groups) can_access uses the resolved branchcodes so listing and direct access agree. The saved reports table shows group titles followed by any ungrouped libraries as "Branch name (CODE)". Test plan: 1. Set LimitReportsBy to Library group 2. Create a library group containing Centerville and Fairfield, tick "Limit report access by group" 3. As a superlibrarian at Centerville, create a report limited to Fairview (not in any group) 4. Saved reports list: the report is hidden 5. Set your library to Fairview, reload the saved reports list 6. The report is visible and the Library limits column shows "Fairview (FRV)" instead of "No limitation" 7. Edit the report and add Centerville to the limit. The column shows the group title followed by "Fairview (FRV)" 8. Log in as a non-manager user at Fairfield and open the report from step 3 by URL. Access is denied 9. prove t/db_dependent/Koha/Reports.t Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #71 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 206697 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=206697&action=edit Bug 42621: (QA follow-up) Always render the column to prevent datatables error The library limit column was only rendered if the syspref was switched on but this would cause a databtables column index mismatch and throw an error. This patch always renders the column and handles the column value based on the syspref value rather than just showing/hiding it Assisted-by: Sonnet 5 (Anthropic) Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Signed Off -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #74 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 207573 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=207573&action=edit Bug 42621: Add a ft_reports column to library_groups Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #76 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 207575 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=207575&action=edit Bug 42621: Handle the new ft_reports column in the UI Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #78 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 207577 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=207577&action=edit Bug 42621: Update reports search to be able to look up by library group Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #80 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 207579 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=207579&action=edit Bug 42621: Add unit test for lib group limits Test plan: Prerequisites 1. Three branches: Centerville, Fairfield, Fairview 2. Admin - Library groups: create root group "Test Group", enable Limit report access by group, add Centerville and Fairfield as child libraries (not Fairview) 3. Create an admin user with manage_report_limits permission (or superlibrarian) at branch Centerville 4. Create regular users with reports + execute_reports only (no manage_report_limits), one at each of Centerville, Fairfield, and Fairview 5. Admin - Administration - Columns settings - Reports - Saved reports (table_reports) - enable the Library limits column (it is hidden by default) Baseline - LimitReportsBy = No restriction 6. Set LimitReportsBy = No restriction 7. Admin user - create Report A - no "Library limitation" field visible, save report with any parameters, content is not important 8. Admin user - Reports list - no "Library limits" column visible even if enabled in column settings. Library mode - regression 9. Set LimitReportsBy = Library 10. Admin user - Reports list - "Library limits" column visible (if enabled in column settings) 11. Log in as the Fairview user - Reports list - "Library limits" column not visible as user doesn’t have manage_reports_limit permission 12. Admin user - edit Report A - Library limitation field should be visible - set limit to Centerville - report saves with Centerville limit 13. Fairview user - Reports list - Report A not visible 14. Regular user at Centerville - Reports list - Report A visible 15. Regular user at Centerville - edit Report A - save - limits preserved (fieldset not shown; backend preserves existing limits silently) 16. Admin user - Report A visible with "1 library limitation" tooltip showing Centerville. Delete Report A Library group mode - setup and limits column 17. Set LimitReportsBy = library_group 18. Admin user - Reports list - "Library limits" column still visible 19. Regular user at Centerville - Reports list - "Library limits" column not visible 20. Admin user - create Report B, set limit to Centerville - "Library limitation" fieldset visible, saves with Centerville as the limit 21. Admin user - Reports list - Report B shows "Test Group" in limits column 22. Admin user - create Report C with no limit - Report C shows "No limitation" in limits column Library group mode - access by group membership 23. Fairfield user - Reports list - Report B visible (Fairfield is in the same group as Centerville). Report C also visible (no limitation) 24. Fairview user - Reports list - Report B not visible (Fairview not in group) 25. Fairview user - navigate directly to Report B URL - access denied 26. Fairview user - Reports list - Report C visible (no limitation) Library group mode - ft_reports flag required 27. Admin - Library groups: disable "Limit report access by group" on "Test Group" 28. Regular user at Fairfield - Reports list - Report B no longer visible as it was limited to Centerville 29. Admin user - Report B limits column - shows "No limitation" 30. Re-enable the flag - Fairfield can see Report B again Library group mode - non-admin save behaviour 31. Regular user at Centerville - create new Report D - save - Report D automatically limited to Centerville (backend sets own branch; no fieldset shown). Verify by viewing the saved reports table as the Admin user - should show Test group as the limitation 32. Regular user at Centerville - edit Report B - save - existing limits preserved unchanged Switching modes 33. With Report B limited to Centerville and LimitReportsBy = library_group - Fairfield can access 34. Switch to LimitReportsBy to Library - Fairfield can no longer access Report B (exact branch match only) 35. Switch back to library_group - Fairfield can access Report B again 36. Switch to none - all reports accessible; no limits column or fieldset anywhere Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #82 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 207581 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=207581&action=edit Bug 42621: (QA follow-up) Display and enforce limits to ungrouped libraries When LimitReportsBy is set to library_group and a report is limited to a library that is not in any group with "Limit report access by group" enabled, the limit was enforced in the saved reports list but the "Library limits" column showed "No limitation". Direct access via can_access also ignored the limit entirely, because it only checked qualifying groups. An ungrouped library is now treated as a group of one. Two helpers are added to Koha::Object::Limit::LibraryGroup: - ungrouped_library_limits returns the limited libraries that are not members of any qualifying group - library_group_limit_branchcodes returns every branchcode the limit resolves to (stored branchcodes plus all members of qualifying groups) can_access uses the resolved branchcodes so listing and direct access agree. The saved reports table shows group titles followed by any ungrouped libraries as "Branch name (CODE)". Test plan: 1. Set LimitReportsBy to Library group 2. Create a library group containing Centerville and Fairfield, tick "Limit report access by group" 3. As a superlibrarian at Centerville, create a report limited to Fairview (not in any group) 4. Saved reports list: the report is hidden 5. Set your library to Fairview, reload the saved reports list 6. The report is visible and the Library limits column shows "Fairview (FRV)" instead of "No limitation" 7. Edit the report and add Centerville to the limit. The column shows the group title followed by "Fairview (FRV)" 8. Log in as a non-manager user at Fairfield and open the report from step 3 by URL. Access is denied 9. prove t/db_dependent/Koha/Reports.t Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #84 from Andrew Fuerste-Henry <andrew@bywatersolutions.com> --- Created attachment 207583 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=207583&action=edit Bug 42621: (QA follow-up) Always render the column to prevent datatables error The library limit column was only rendered if the syspref was switched on but this would cause a databtables column index mismatch and throw an error. This patch always renders the column and handles the column value based on the syspref value rather than just showing/hiding it Assisted-by: Sonnet 5 (Anthropic) Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |rel_26_11_candidate -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Pedro Amorim (ammopt) <pedro.amorim@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Patch doesn't apply CC| |pedro.amorim@openfifth.co.u | |k -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #207573|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #207575|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #207577|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #207579|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #207581|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #207583|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #86 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 208650 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208650&action=edit Bug 42621: Add a ft_reports column to library_groups Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #88 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 208652 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208652&action=edit Bug 42621: Handle the new ft_reports column in the UI Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #90 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 208654 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208654&action=edit Bug 42621: Update reports search to be able to look up by library group Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #92 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 208656 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208656&action=edit Bug 42621: Add unit test for lib group limits Test plan: Prerequisites 1. Three branches: Centerville, Fairfield, Fairview 2. Admin - Library groups: create root group "Test Group", enable Limit report access by group, add Centerville and Fairfield as child libraries (not Fairview) 3. Create an admin user with manage_report_limits permission (or superlibrarian) at branch Centerville 4. Create regular users with reports + execute_reports only (no manage_report_limits), one at each of Centerville, Fairfield, and Fairview 5. Admin - Administration - Columns settings - Reports - Saved reports (table_reports) - enable the Library limits column (it is hidden by default) Baseline - LimitReportsBy = No restriction 6. Set LimitReportsBy = No restriction 7. Admin user - create Report A - no "Library limitation" field visible, save report with any parameters, content is not important 8. Admin user - Reports list - no "Library limits" column visible even if enabled in column settings. Library mode - regression 9. Set LimitReportsBy = Library 10. Admin user - Reports list - "Library limits" column visible (if enabled in column settings) 11. Log in as the Fairview user - Reports list - "Library limits" column not visible as user doesn’t have manage_reports_limit permission 12. Admin user - edit Report A - Library limitation field should be visible - set limit to Centerville - report saves with Centerville limit 13. Fairview user - Reports list - Report A not visible 14. Regular user at Centerville - Reports list - Report A visible 15. Regular user at Centerville - edit Report A - save - limits preserved (fieldset not shown; backend preserves existing limits silently) 16. Admin user - Report A visible with "1 library limitation" tooltip showing Centerville. Delete Report A Library group mode - setup and limits column 17. Set LimitReportsBy = library_group 18. Admin user - Reports list - "Library limits" column still visible 19. Regular user at Centerville - Reports list - "Library limits" column not visible 20. Admin user - create Report B, set limit to Centerville - "Library limitation" fieldset visible, saves with Centerville as the limit 21. Admin user - Reports list - Report B shows "Test Group" in limits column 22. Admin user - create Report C with no limit - Report C shows "No limitation" in limits column Library group mode - access by group membership 23. Fairfield user - Reports list - Report B visible (Fairfield is in the same group as Centerville). Report C also visible (no limitation) 24. Fairview user - Reports list - Report B not visible (Fairview not in group) 25. Fairview user - navigate directly to Report B URL - access denied 26. Fairview user - Reports list - Report C visible (no limitation) Library group mode - ft_reports flag required 27. Admin - Library groups: disable "Limit report access by group" on "Test Group" 28. Regular user at Fairfield - Reports list - Report B no longer visible as it was limited to Centerville 29. Admin user - Report B limits column - shows "No limitation" 30. Re-enable the flag - Fairfield can see Report B again Library group mode - non-admin save behaviour 31. Regular user at Centerville - create new Report D - save - Report D automatically limited to Centerville (backend sets own branch; no fieldset shown). Verify by viewing the saved reports table as the Admin user - should show Test group as the limitation 32. Regular user at Centerville - edit Report B - save - existing limits preserved unchanged Switching modes 33. With Report B limited to Centerville and LimitReportsBy = library_group - Fairfield can access 34. Switch to LimitReportsBy to Library - Fairfield can no longer access Report B (exact branch match only) 35. Switch back to library_group - Fairfield can access Report B again 36. Switch to none - all reports accessible; no limits column or fieldset anywhere Signed-off-by: Brendan Lawlor <blawlor@clamsnet.org> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #94 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 208658 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208658&action=edit Bug 42621: (QA follow-up) Display and enforce limits to ungrouped libraries When LimitReportsBy is set to library_group and a report is limited to a library that is not in any group with "Limit report access by group" enabled, the limit was enforced in the saved reports list but the "Library limits" column showed "No limitation". Direct access via can_access also ignored the limit entirely, because it only checked qualifying groups. An ungrouped library is now treated as a group of one. Two helpers are added to Koha::Object::Limit::LibraryGroup: - ungrouped_library_limits returns the limited libraries that are not members of any qualifying group - library_group_limit_branchcodes returns every branchcode the limit resolves to (stored branchcodes plus all members of qualifying groups) can_access uses the resolved branchcodes so listing and direct access agree. The saved reports table shows group titles followed by any ungrouped libraries as "Branch name (CODE)". Test plan: 1. Set LimitReportsBy to Library group 2. Create a library group containing Centerville and Fairfield, tick "Limit report access by group" 3. As a superlibrarian at Centerville, create a report limited to Fairview (not in any group) 4. Saved reports list: the report is hidden 5. Set your library to Fairview, reload the saved reports list 6. The report is visible and the Library limits column shows "Fairview (FRV)" instead of "No limitation" 7. Edit the report and add Centerville to the limit. The column shows the group title followed by "Fairview (FRV)" 8. Log in as a non-manager user at Fairfield and open the report from step 3 by URL. Access is denied 9. prove t/db_dependent/Koha/Reports.t Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #96 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 208660 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208660&action=edit Bug 42621: (QA follow-up) Always render the column to prevent datatables error The library limit column was only rendered if the syspref was switched on but this would cause a databtables column index mismatch and throw an error. This patch always renders the column and handles the column value based on the syspref value rather than just showing/hiding it Assisted-by: Sonnet 5 (Anthropic) Signed-off-by: Andrew Fuerste Henry <andrew@bywatersolutions.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Pedro Amorim (ammopt) <pedro.amorim@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Failed QA --- Comment #98 from Pedro Amorim (ammopt) <pedro.amorim@openfifth.co.uk> --- Hi all, a few blockers here: Setup (for all): 1) Apply the patches, then in `ktd --shell` run `updatedatabase && restart_all`. Blocker 1: fresh installs don't get the new pref, and saved reports crash 1) Run `grep -n "LimitReportsBy" installer/data/mysql/mandatory/sysprefs.sql`. Only `LimitReportsByLibrary` is there, and fresh installs only get prefs from this file. 2) Run `prove t/db_dependent/check_sysprefs.t`. It reports "Too many sysprefs in DB: LimitReportsBy", and the sort check finds `LimitReportsByLibrary` where `LimitReportsBy` is expected. 3) To see what a fresh install would hit, remove the pref: `koha-mysql kohadev -e "DELETE FROM systempreferences WHERE variable = 'LimitReportsBy'"`, then run `restart_all`. 4) Open http://localhost:8081/cgi-bin/koha/reports/guided_reports.pl?op=list. It fails with "Can't call method "unblessed" on an undefined value". 5) Restore the pref as the upgrade left it: `koha-mysql kohadev -e "INSERT INTO systempreferences (variable, value, options, type) VALUES ('LimitReportsBy', 'none', 'none|library|library_group', 'Choice')"`, then run `restart_all`. sysprefs.sql needs `('LimitReportsBy','none')` in place of `('LimitReportsByLibrary','0')`. Blocker 2: the renamed pref breaks check_sysprefs.t on upgraded sites 1) Run `koha-mysql kohadev -e "SELECT variable, value, options, type FROM systempreferences WHERE variable = 'LimitReportsBy'"`. `options` is `none|library|library_group` and `type` is `Choice`. 2) Temporarily fix blocker 1, so `check_sysprefs.t` gets past it: `sed -i "s/('LimitReportsByLibrary','0')/('LimitReportsBy','none')/" installer/data/mysql/mandatory/sysprefs.sql` 3) Run `prove t/db_dependent/check_sysprefs.t`. It fails with "LimitReportsBy has 'options' set in DB, must be NULL!" and the same for 'type'. 4) Undo the temporary fix: `git checkout installer/data/mysql/mandatory/sysprefs.sql` Since Bug 41834, the atomic update must only rename `variable` and set `value`. Blocker 3: the list and direct access disagree with nested groups 1) Open http://localhost:8081/cgi-bin/koha/admin/preferences.pl?op=search&searchfield=LimitReportsBy, set it to 'Library group' and click 'Save all Reports preferences'. 2) Open http://localhost:8081/cgi-bin/koha/admin/library_groups.pl, click 'New group', title it 'Reports test', tick 'Limit report access by group' and save. 3) On 'Reports test', click 'Add library' and add Centerville. 4) On 'Reports test', click 'Actions' > 'Add sub-group' and create 'Sub'. On 'Sub', click 'Add library' and add Fairfield. 5) As koha, open http://localhost:8081/cgi-bin/koha/reports/guided_reports.pl?op=add_form_sql and save a report 'Limited to Fairfield' with SQL `SELECT 1`, selecting only Fairfield in 'Library limitation'. 6) Do the same for a report 'Limited to Centerville', selecting only Centerville. 7) Create a staff user at Centerville and one at Fairfield, each with only 'catalogue' and 'Reports' > 'execute_reports'. 8) Log in as the Centerville user and open http://localhost:8081/cgi-bin/koha/reports/guided_reports.pl?op=list. 'Limited to Fairfield' is listed, but clicking 'Run' gives "Access denied". 9) Log in as the Fairfield user and open the same list. 'Limited to Centerville' isn't listed, but opening http://localhost:8081/cgi-bin/koha/reports/guided_reports.pl?id=<its id>&op=run runs it. Should a group mean the whole tree under the root group where 'Limit report access by group' is ticked, or only a library's immediate parent group? Whichever it is, the list and direct access need to use the same rule. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 --- Comment #99 from Matt Blenkinsop <matt.blenkinsop@openfifth.co.uk> --- Created attachment 208804 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=208804&action=edit Bug 42621: (QA follow-up) Add LimitReportsBy to sysprefs.sql and fix the atomic update sysprefs.sql still listed LimitReportsByLibrary, so a fresh install had no LimitReportsBy row. get_saved_reports then compared an undefined preference value and crashed on the saved reports list with "Can't call method unblessed on an undefined value". check_sysprefs.t also failed with "Too many sysprefs in DB: LimitReportsBy". The atomic update also set options and type on the renamed preference. Since bug 41834 these columns must be NULL in the database, the YAML file owns them. The update now only renames the variable and converts the value. The stale preference name is also replaced in Reports/Guided.t. Test plan: 1. grep -n "LimitReportsBy" installer/data/mysql/mandatory/sysprefs.sql shows ('LimitReportsBy','none') 2. In ktd --shell: updatedatabase && restart_all 3. koha-mysql kohadev -e "SELECT variable, value, options, type FROM systempreferences WHERE variable = 'LimitReportsBy'" shows value none and NULL for options and type 4. prove t/db_dependent/check_sysprefs.t 5. Open the saved reports list, it loads without error Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Andrew Fuerste-Henry <andrew@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Text to go in the| |This enhancement allows release notes| |reports access to be | |limited by library groups. | |The system preference | |LimitReportsByLibrary is | |renamed to LimitReportsBy | |and the new option "library | |groups" is added. In | |library groups setup in | |administration, a new group | |feature of "Limit report | |access by group" is added. | |When the system preference | |is set to limit by groups, | |a report with a library | |limitation that includes | |any given library will also | |be accessible to users from | |other libraries sharing a | |report-limiting group with | |the first library. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Pedro Amorim (ammopt) <pedro.amorim@openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to main Version(s)| |26.11.00 released in| | -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42621 Lucas Gass (lukeg) <lucas@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to main |Needs documenting --- Comment #102 from Lucas Gass (lukeg) <lucas@bywatersolutions.com> --- Enhancement, no 26.05.x backport. -- You are receiving this mail because: You are watching all bug changes.