Take a look at the following reference links -
https://support.atlassian.com/jira-software-cloud/docs/best-practices-for-workflows-in-jira/
https://idalko.com/jira-workflow-best-practices/
https://support.atlassian.com/jira-work-management/docs/how-to-create-workflows/
The concept of WF management is essentially the same regardless if it is for Jira Software/Jira Services Mgmt/Jira Work Mgmt applications. The biggest differences are Company-Managed or Team-Managed. Where the Team-Managed type project's WF customization/statuses/designs are not sharable between projects.
Based on my experiences, I would recommend the following general rules -
1) Keep WF simple.
2) When creating new WF statuses, consider a) make your status name short and generic to support the idea of re-use across many projects b) avoid creating status which only supporting one specific team/project c) customize the WF to use the common statuses and utilize design of transitions to handle different situation as much as possible.
With more practices/experiences, you will soon become a master on how to design/manage WFs for your company.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Viasat Inc.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.