Agile Simplified Workflow unavailable

Hello,
I'm pretty sure that my project meet all the criteria to bne able to switch a board simplified workflow:

  • There is only one project being viewed by your board (to check this, look at the board's filter); and
  • That project uses a JIRA workflow scheme which only has one workflow for all issue types; and
  • Your workflow only uses Post Functions, Validators, and Conditions which are provided by Atlassian (not any which are provided by add-ons); and
  • You have the 'JIRA Administrators' global permission; and
  • The existing workflow has at least one outgoing transition for each status; and
  • You are using JIRA version 5.0.4 or later (please see Supported Platforms).


Still, I Keep getting the "Agile Simplified Workflow unavailable". I don't know what else to check.
Ideas?

3 answers

1 accepted

10 votes
Anna Cardino Atlassian Team Apr 19, 2014

Hello Claudio,

Based on the description that you've mentioned, it looks like you're running into a bug, though a fairly minor one.

Basically, one of the requirements is "That project uses a JIRA workflow scheme which only has one workflow for all issue types". The bug is that this "assumes" that you didn't individually assign the same workflow to all issue types.

So in this case, to fix this, you'll want to basically:

* Edit the Workflow Scheme

* Remove all the assigned Issue Types (that is, click the "x" next to each issue type)

* Do this for all issue types, leave just "All Unassigned Issue Types"

* Click Publish

This is a bug, as JIRA should be able to respect your original setup. For you reference, please see GHS-8720.

Hope I was able to help you.

Regards,

Monique

It would be good if this workaround was attached on https://confluence.atlassian.com/display/AGILE/Using+JIRA+Agile+Simplified+Workflow?src=search#UsingJIRAAgileSimplifiedWorkflow-whyNot.

I just spend an hour going through all criteria, being lost and frustrated because of this issue which I could not have known was blocking this.

I agree. The documentation is lacking. And besides, there should be some kind of diagnostic tool to help with this, it's terribly aggravating to poke in the dark like the current system requires you to do.

Good job u can use the default jira workflow

August 2016, still a problem... sad

We were seeing this problem today.  

 

The problem was that the project had been re-named, and the Filter was incorrect.  We fixed the filter, and we were able to assign the simplified workflow.

 

 

Thanks Veracode NOC, I faced the same issue and your pointer helped to solve it.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Sarah Schuster
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

12,070 views 15 13
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