Bug 27679 - The notices and slips management area should be moved to 'Administration'
Summary: The notices and slips management area should be moved to 'Administration'
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-02-11 11:19 UTC by Martin Renvoize
Modified: 2024-03-18 12:31 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Renvoize 2021-02-11 11:19:29 UTC
As the title says, the Notics and Slips "tool" isn't really a tool.. it's a system administration task.. so it should live under administration.
Comment 1 Katrin Fischer 2021-02-11 11:45:00 UTC
I am not sure about that one. I am thinking about who has the permission to change this - and in almost all of our libraries a lot of people have notices and slips permissions, but only one or 2 have permission for changing anything in the administration module (exceptions are funds and budgets, but one could argue a bit about those not being "quite" in administration either)

Also, the way it is now, they are together with the overdue notice triggers.

With the new granular permissions it's easier of course to move it than it was before.
Comment 2 Katrin Fischer 2023-01-23 22:17:54 UTC
Martin, are you still interested in this one? Would love to get some more opinions.
Comment 3 Andrew Fuerste-Henry 2024-03-11 13:51:31 UTC
I can see the argument that notice/slip content and overdue notice triggers should both be in Administration rather than Tools. Both seem roughly analogous to the circulation rules -- they define how circulation should behave, rather than giving one tools with which to manage patrons or checkouts. But they'd definitely need distinct permissions; we have to assume there are folks who currently have access to edit notices but don't have any other admin access.
Comment 4 Martin Renvoize 2024-03-18 12:31:30 UTC
Still interested.. generally I'm interested in any efforts to simplify and clarify UI/UX and this counts as that to me.

We do indeed need nice fine-grained permissions as part of that though.