We have migrated from JIRA 3.13.5 to 5.2.11 and have run into the following problem:
I have a 'Send to FA' transition with a 'FA' destination step. The FA step has the property key jira.permission.assignable.group set to the value FA. In 3.13.5 this would limit the assignee choices to users in the FA group, thus preventing an issue at the 'FA' step from being assigned to a user not in the FA group.
However, in 5.2, I can pick the current assignee (from the Suggestions list) and that user will be the assignee at the FA step (even though they aren't in the FA group). The log shows this:
assignable not granted by workflow perm granting assignable to Group 'FA' /secure/IssueAction!default.jspa [atlassian.jira.security.WorkflowBasedPermissionManager]
assignable granted by permission scheme but DENIED by workflow
Is there a way to disable assignee Suggestions? Shouldn't the suggested assignees also meet the jira.permission.assignable.group criteria?
Thanks for your help.
On a side note: There is a way to switch to a full assignee drop down box (no need to start typing a user's name)...but the problem remains. I can still select the current assignee or suggested users even if they are not in the group specified.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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