My context is as follow :
When the current assignee has to perform a transition it has to assign among allowed Assignees restricted by the Workflows Properties.
The list of Assignables is correctly built depending on properties, but the current is always proposed even if he is not assignable.
Any idea how to process ?
Or is there a bug ?
With regards to the current assignee is always proposed by the transition screen, this would indeed be the expected behavior of JIRA. This behavior can also be seen from edit issue screen whereby the fields are pre-populated with the existing values from the database.
The properties (jira.permission.assignable.projectrole.1=10100;jira.permission.assignable.projectrole.1=10101; ...) will be taken into consideration after the transition is attempted and not when the edit or transition screen is brought up.
As of now, I can't think of a way to remove the current field values during the edit or transition screen. This is not a feature that is natively available in JIRA. Perhaps there are some plugins that can achieve this.
I hope my explanation provides you with information on why the behavior is happening as observed right now.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
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