When it comes to workflows, one of the biggest challenges is ensuring that users work in a structured manner and make proper use of the system. The challenges of getting people to use Jira workflows in a structured manner If many teams start using different workflows and naming conventions, then it might become pretty confusing when these teams have to start collaborating or when members migrate to new teams. A third drawback of over-customization is the communication disconnect between teams.This can be quite challenging if you add too many customizations. They’ll also have to ensure that the instance continues to function correctly (including with apps and other integrations).Overdoing it is probably not a good idea. If you do want to deploy customization, then your admin will need to build and maintain the changes.This will allow you to ensure that everything is correctly logged on the system, hence offering new insights into exactly how your processes function. Benefits and drawbacks to changing workflowsĬreating Jira workflows to match the way you work comes with the benefit of making Jira far more useful for you and your team. They allow you to move Issues around the system exactly as you need. Of course, if you’re using Jira for other purposes, such as a CV database, then workflows might be even more useful. This way you’ll be mapping how tasks are processed and dealt with while wiping out redundancy. It’s all tracked and logged automatically through workflows. There’s no need to drop a colleague an email to let them know that a task has become available for them. Jira enables users to seamlessly log tasks and information. And you could see a big productivity boost as a result. If you can use existing elements and features provided by Jira with minimal hassle, then it is the simplest way to get ahead.īut if it means that the system simply doesn’t reflect the way that you work, then it might be essential to deploy customization. So, when considering customization, it’s important to think about precisely what you’re doing and why.Īnd clear communication is essential. Just make sure not to overdo it when creating unique workflows, though, as this will limit interoperability as well as create other issues – as explained in our blog post on the worst (common) advice for Jira.
Separate teams might also naturally benefit from having their own work patterns and requirements built into Jira. All kinds of teams use Jira – from customer support to HR to developers. While you might use Jira’s standard workflow to be able to simply move an Issue from “Open,” to “In Progress” to “Complete,” things are often more complicated in the real world.įor example, if work needs to be approved then you may need to add additional statuses to reflect “Awaiting Approval,” “Review In Progress” and “Review Complete”.Īnother reason to customize workflows is the diversity of teams. Why Create a New Jira WorkflowĬreating a new Jira workflow allows you to adapt the system to exactly how your team works. However, it might be a better choice to create your own custom Jira workflow. JWM is a new and improved Jira product for non-technical teams. Process management: A workflow structure that comes with multiple statuses and resolutions reflecting the complexity of business and development processes.Īll these workflows are now available in Jira Work Management as well.Project management: A slightly more complex workflow, which includes an “In Progress” status to better mark work on the task.Task management: The simplest possible workflow, to get tasks done as soon as possible.And you’ve already gone from one end of the workflow to the other. Then, when the task is finished, you can mark it as being “Done”.
0 kommentar(er)
