Opened 17 years ago
Closed 16 years ago
#6833 closed enhancement (worksforme)
Option to Restrict the Ticket Admin panel to TRAC_ADMIN
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | admin/console | Version: | 0.11b1 |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Can you add an option to restrict the Ticket System Admin screen so that we can either specify TRAC_ADMIN or TICKET_ADMIN. Right now we want to allow the TRAC_ADMIN privilege so that the users can delete attachments and modify descriptions, but we do not want the users to have the ability to modify stuff like components, resolutions, priorities, etc, etc.
To get around it for now I modified the admin.py file, but if I upgrade the code those changes will be lost every time.
Attachments (0)
Change History (4)
follow-up: 2 comment:1 by , 17 years ago
Milestone: | 0.11 |
---|
comment:2 by , 17 years ago
Replying to cboos:
Right now we want to allow the TRAC_ADMIN privilege so that the users can delete attachments and modify descriptions
You meant TICKET_ADMIN in the above. But there's already tickets for those two specific situations: #3163 and #948.
I think it's better to go in that direction (and I'd really favor doing #3163 asap, now that we have #2945) than to change the meaning of TICKET_ADMIN. What do others think?
Yes I did mean TICKET_ADMIN. I do agree on the changes made on 3163, however I think it should also be optional to the Trac admin on who should have the ability to administor those ticket components. Some admins may want to only allow TRAC_ADMIN but others may want to allow TICKET_ADMINs. Probably depends on who is using trac and what they are using it for. In our case we only want to allow TRAC_ADMIN the privilege to make changes to administrative section.
comment:3 by , 16 years ago
Milestone: | → 2.0 |
---|---|
Owner: | removed |
comment:4 by , 16 years ago
Milestone: | 2.0 |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
Replying to jason.trahan@…:
Right now we want to allow the TRAC_ADMIN privilege so that the users can delete attachments and modify descriptions, but we do not want the users to have the ability to modify stuff like components, resolutions, priorities, etc, etc.
Edition of the description can be enabled with TICKET_EDIT_DESCRIPTION
. Removal of attachments can be enabled with ATTACHMENT_DELETE
(you'll need to do that with fine-grained permissions, though). So you don't need to give your users TICKET_ADMIN
.
At this point, I don't see a reason to add another special case for the ticket admin panels.
You meant TICKET_ADMIN in the above. But there's already tickets for those two specific situations: #3163 and #948.
I think it's better to go in that direction (and I'd really favor doing #3163 asap, now that we have #2945) than to change the meaning of TICKET_ADMIN. What do others think?