As a Jira administrator and consultant, I’ve seen plenty of horrendous workflows. The worst had 39 statuses and 1,007 transitions. It’s the longest workflow I’ve seen. And no, I did NOT build this one!
The workflow had 39 statuses and 1,007 transitions! It was a development workflow, and it was used by all issue types and every Jira project. The status names are blurry in the screenshot above, but they were equally hard to read in Jira as well.
What do you notice about this workflow? First, it’s impossible to follow. How do you know where you are in the process and how close the issue is to completion? The diagram is hard to see, for both admins and users. The status names are long and likely truncated in different Jira locations. Finally, there were five statuses in the green “Done” status category. For me, that’s four too many.
This workflow was build to make sure each team participated in each phase of a development request. Instead of the generic “In Progress” status, they had one custom status for every team like “In Progress [Customer Service]”, “In Progress [Product]”, and “In Progress [Dev]”. A better way to manage this would be to use the “Assignee” field, sub-tasks, or custom notifications to solve visibility worries.
I worked with this customer, and we were able to get this workflow down to only seven statuses and 19 transitions. Their users and admins are much happier now and the company didn’t sacrifice participation or visibility.
Rachel Wright
Author, Jira Strategy Admin Workbook
Industry Templates, LLC
Traveling the USA in an RV
46 accepted answers
3 comments