Jira Agile managed workflow loses permissions

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?

1 answer

1 accepted

2 votes

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.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,277 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot