Opened 17 years ago
Closed 8 years ago
#5425 closed enhancement (worksforme)
Make the state transition dependant on group membership in addition to the boiled down group permissions in workflows
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | devel |
Severity: | normal | Keywords: | workflow permissions |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
That would make it possible to only allow users that are members of the group user_group to perform the workflow action.
disapprove = solved -> reopened disapprove.name = Disapprove Solution disapprove.permissions = user_group # instead of TICKET_APPEND disapprove.operations = del_owner
Attachments (0)
Change History (7)
comment:1 by , 17 years ago
Summary: | Make the state transition dependant on group membership in addition to the boiled down group permissions → Make the state transition dependant on group membership in addition to the boiled down group permissions in workflows |
---|
comment:2 by , 17 years ago
follow-up: 4 comment:3 by , 17 years ago
Milestone: | 0.11.1 → 0.12 |
---|
This will anyway have to wait as improvements in the user system are needed on the API level. See #6703 comments and further links to tickets and discussions for more information.
comment:4 by , 14 years ago
comment:5 by , 9 years ago
Owner: | removed |
---|
comment:6 by , 8 years ago
#11839 allows groups and permissions to be specified in the set_owner
attribute.
comment:7 by , 8 years ago
Milestone: | next-major-releases |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
After spending some time on this, I realized it's a case that should be handled by ExtraPermissionsProvider. Define a permission action, which for the example might be TICKET_DISAPPROVE
. Assign that permission action to the groups that you'd like to perform the workflow action. See TracWorkflow@73.
I vote for this issue