Workflow Status limits

[Julie Lin]

Jira Community

I'm using jira 7.8.  Where do I configure the max number of status allowed in a workflow?  Is there a limit?

[Nic Brough -Adaptavist- · Accepted solution]

I don't know if there's a limit somewhere if you go past 150 in a workflow, but I can tell you that if you've got 150 status in your workflow, you've got an over-complicated and almost certaintly broken worklow and process.

[Julie Lin]

agree ,  

one project has 11 and workflow button works fine

another project had 14 and workflow button is NOT visible.

[Nic Brough -Adaptavist-]

Suggests the user doesn't have the right to transition the issue in that project.

[Julie Lin]

"transition issues"  is granted to "jira-users"  group and "users" project role   

in fact, the problem project allows "transition issues" to more groups.

[Nic Brough -Adaptavist-]

So, I'm looking at a Cloud system with 18 transitions and a Server with 35.  Both are showing fine, when the current user has "transition issue" permission.  There's no "limit", there is something else wrong with it.

So, let's look at the issues more closely now we've ruled out the obvious: 

• Is this happening for all issues in the project that are in that status?
• Is it limited to one issue type?  (If you have more than one workflow in the project)
• Take the issue you looked at when raising this problem.  Look at the workflow diagram for it from the issue.  What transitions does it have out of the current status, and (you'll need admin to do this bit) what are the conditions on them?  (In fact, if you can find only one transition out that has no conditions, that's enough to show it's not condition problems)

[Julie Lin]

happens for all issue types in the project

i see 2 transitions out of the current status of "waiting approval".  It  can go to "approved" or "rejected"  with no conditions.

if its not a permission issue with the user or the transition conditions, what else could it be?

[Nic Brough -Adaptavist-]

There is only one other thing than conditions that could cause this, which is a very broken data set.

Can you run the integrity checker for the workflow and status related inconsistencies?  If this is the problem, it will list the issues you are not seeing the workflow on.  If the problem is not this, then I'm afraid it has to be misreading the permissions and conditions.

[Julie Lin]

good news, no integrity issues

bad news, now sure how it's misreading permissions.   we do not use conditions.

[Nic Brough -Adaptavist-]

There is nothing else that would do this.

We would need to see all the exact settings you have for permissions and conditions in your workflows, and if they're ok, there's no option but a support request with Atlassian.

[Zvika Melamed]

We use statuses as a timeline on weekly granularity in a Board view. Very convenient for project management, works great, no add-ons needed.

The only concern is - limitation of statuses ;-)

[Julie Lin · Accepted solution]

I have resolved this issue.  

Apparently i need to click on "allow all statuses to transition to this one"

before they would show up.  I thought i had tried that before, but now it's working.