Jira Agile managed workflow loses permissions

[Zach Newman]

When creating a Jira Agile (greenhopper) dashboard, I chose the agile managed simplified workflow in order to add custom statuses. This workflow does not preserve the project permissions, allowing anonymous users to execute transitions. Is there any way to avoid this besides manually adding all the transition conditions and switching workflows?

[Nic Brough -Adaptavist- · Accepted solution]

Correct. The simplified workflow does not have much in the way of conditions because it simply cannot know what you might want on there. Your project admins could change it at any time, and the choice Atlassian have had to make is between "map columns, keep it simple for the users" and "every time an admin adds or moves a column, ask them about conditions and all the other complexities"

I think you've already named your only options - manually add conditions (bearing in mind you'll need to do it every time a project admin adds a new column!) or move back off the simplified workflow.