I tried to grant a permission to assign issues to a project role for one step of my workflow.
The rest of the WF I want the permission to be denied. So in permissions I excluded the role and then set the properties for the chosen step as follows:
Property Key: jira.permission.assign.projectrole
Property Value: 10200
The user with the respective role still cannot assign issues in the given workflow step. Any idea what might be wrong?
The thing is similar to the permission restriction through permission scheme: once you use “denied” in the property, the permission before the denied word, is restricted for everyone, no matter what you add after it (for example jira.permission.comment.denied means the comment feature is disabled at state you add the property)
Have a look at this site, is really usefull: http://www.j-tricks.com/tutorials/permissions-based-on-workflow-status”
In your case, what do you need? Restrict assign permission to only one transition? To only one project role?
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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