Building workflows in Jira can be a struggle sometimes, depending on the expertise of the person on charge or the tool configuration. Every case is unique! Through this blog post, we’ll show how to think about complexity when it comes to creating new Jira workflows.
Workflows are the pipes of Jira, the single reason why Atlassian’s signature tool can be implemented for a potentially unlimited number of different scenarios, and a vital part of project configuration.
Workflows come in all sizes and degrees of complexity. There are simple workflows like this:
And workflows that absorb overly complicated processes, like this one:
Some people criticize Jira because poorly designed workflows can take a toll on performance and create a solid barrier against lean processes and fast change. They’re wrong! Blame the designer, not the tool: if your processes are monsters, no tool will magically transform them into heroes.
But when is a process a monster? In other words, when does a process become unmanageable? When is it too much for the people who must follow it, and when is it too much for the tool? And does one problem take to the other?
The answers to these questions are not obvious. To help you determine what makes sense in your context, in this article we’re going to offer some clues and best practices for workflow design in Jira and you can finish the read, with more details about each bullet point, at our blog, by clicking the button below:
1. Use Jira Core for corporate non-tech processes.
2. Workflow complexity doesn’t depend on the number of statuses.
3. Calculate the complexity of the tool from the actions within each status.
4. Calculate the complexity for the user from the transition options for each status.
5. Inform the user on the implications of her action.
Click the button below to read the full blog post!
