Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Agile Simplified Workflow unavailable

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.

4 answers

1 accepted

12 votes
Answer accepted
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.



It would be good if this workaround was attached on

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

Still occurs in JIRA 7.9.0.

How about adding a reference to the corresponding documentation page?

2020 v8.blah and it is still a bug. 

Like # people like this

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.

2021 and I still want to jab my eyes out with very pointy sticks. I agree with the need for better documentation!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Bitbucket Smart Commits vs. Genius Commits - What's the difference?

If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...

114 views 0 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you