-
Suggestion
-
Resolution: Unresolved
-
None
-
3
-
6
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.
At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.
I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
dmeyer@atlassian.com
Product Manager, JIRA Platform
Right now it appears that the Assign Permission is all or nothing.
We would like force the "Assign To" functionality to limit the list of users to only be in the user group defined.
Thus, if the workflow step defined assigning to a developer, the user list will only display the list of developers. If the workflow step is to assign to a QA Engineer, the QA Engineer would only have assign-permission to assign to another QA Engineer.
If would be even better if we can configure based on the user's group to specify which group of users should show. For example:-
User group A able to assign ticket to only user in group A
User group B able to assign ticket to users from group A and B
- duplicates
-
JRASERVER-5658 Assignment of tasks to be limited to a certain group of users.
- Closed
-
JRASERVER-6381 Permissions per workflow step / state
- Closed
- is incorporated by
-
JRASERVER-3417 Hiding issue fields for some users /user groups
- Closed
- is related to
-
JRASERVER-6053 restrict assignees by workflow
- Closed
- relates to
-
JRACLOUD-6126 Limit "Assign To" list to specific user group
- Closed
-
JRASERVER-5658 Assignment of tasks to be limited to a certain group of users.
- Closed