The idea would be to create a certain type of permission for a user/group or project role (whatever works I guess) which grants the permission to assign issues, but only to a select group of people.
Here is an example of how this would be used:
Let's say we have two teams of people working on the same project but with different goals. Team A is developing phone applications and team B web applications. Each team has lead and each is related, but the leader from Team A should only be able to assign issues to members of team A and likewise.
Is this possible?
Maybe with properties in statuses you can do a workaround:
Replace example with group=group, role=role, user=username, which you dont want to assign issues.
This link might help you: http://www.j-tricks.com/tutorials/permissions-based-on-workflow-status
Take note that you should make a different workflow for different combination of assignable groups and the user which assign issues.
Correcting, you cant deny a permission for a user/role/group etc, you deny a permission for all users.
The workaround would be a blank assignable user permission in the scheme and grant that permission to only the groups you want to be assigned with the property.
Sorry for the mistake.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Rachel Wright (Jira Genie), @Billy Poggi (AUG NOVA, DC), and @Dana Jansen (Confluence Queen) are just some of the folks that lead one of the world's most active Atlassian User Group (AUG)....
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs