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.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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