nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What are the best practices we should follow when creating or editing a Jira workflow?

Prajwal Sapat

I'm currently working with Jira workflows and want to know about best practices we should follow when we create and edit workflow.

I like to know:

1. How can we ensure workflows remain simple and user-friendly?

2. What are common mistakes to avoid?

3. How can we manage workflow changes without disrupting ongoing projects?

Looking forward to insights and suggestions!

Accepted answers

John Funk

Hi Prawal,

1. That depends on you keeping it that way. :-) Try to keep the naming of statuses fairly generic and reuse them across other workflows instead of creating very unique names. Use the same workflow as much as you can (shared across projects) and use Conditions to help with that. So one transition might apply to one project and not another - don't create separate workflows for those, just use a condition for the project, for example.

2. Most making things too complicated by adding too many statuses. If you don't need to report about every single status/step in the workflow, then simplify it with fewer statuses. Use automation to do some auto transitioning also. I like to keep things linear while others like to have the freedom to move back and forth between statuses. Define that up front for the flow.

3. You can make copies of the workflows, test them on a test project and then sub out the workflows in the ongoing projects when it is ready.

I hope that helps!

All comments

Sushant Verma

Hi @Prajwal Sapat

Welcome to the community!

When creating or editing Jira workflows, it's best to keep them simple and intuitive by using clear status names and minimizing unnecessary transitions. Avoid common mistakes like overcomplicating workflows, ignoring user feedback, or making changes without documentation. To manage workflow updates smoothly, always test changes in a cloned version first, communicate updates to users, and apply changes during low-activity periods to avoid disruption. These practices help maintain usability, scalability, and alignment with team processes.

You can follow below document for more information : https://support.atlassian.com/jira-software-cloud/docs/best-practices-for-workflows-in-jira/

Regards,
Sushant Verma

John Funk

Hi Prawal,

3. You can make copies of the workflows, test them on a test project and then sub out the workflows in the ongoing projects when it is ready.

I hope that helps!

Jasmeet Kaur_xrxtha

Hello @Prajwal Sapat

Welcome to the Atlassian Community!

To understand the best practices one should follow when creating and editing workflow, kindly refer to the following documents:

Thank you!

Chitra Nagdeo

Hey @Prajwal Sapat ,

Welcome to Atlassian Community!

Here are best practices and insights for creating and editing Jira workflows, focusing on simplicity, avoiding common mistakes, and managing changes smoothly:

1. Ensuring Workflows Remain Simple and User-Friendly

Keep it Lean: Limit the number of statuses and transitions to only what’s essential. Overly complex workflows can confuse users and slow down processes. Start simple and add complexity only when there’s a clear need.
Use Clear Naming Conventions: Make sure statuses and transitions are named consistently and intuitively so everyone understands what each step means.
Test Before Publishing: Always test new or updated workflows in a staging project or with a small group before rolling out to everyone. This helps catch issues early.

2. Common Mistakes to Avoid

Overcomplicating the Workflow: Adding too many statuses, transitions, or conditions can make workflows hard to follow and maintain. Stick to what’s necessary for your process.
Ignoring Team Needs: Designing workflows in isolation, without input from end users, often leads to poor adoption and frustration. Always involve your team in the process.
Inconsistent Naming: Using unclear or inconsistent names for statuses and transitions can cause confusion. Standardize your naming conventions.
Failing to Test: Not testing workflows before going live can result in bottlenecks or errors that disrupt work.
Not Considering Permissions: Overlooking permission settings can lead to security issues or users being unable to perform necessary actions.
Neglecting Regular Cleanup: Letting unused workflows, statuses, or custom fields accumulate can clutter your Jira instance and make it harder to manage

3. Managing Workflow Changes Without Disrupting Ongoing Projects

Edit Inactive Workflows When Possible: Make changes to a copy or an inactive version of the workflow, then activate it when ready. This avoids impacting live projects during editing.
Use Drafts for Active Workflows: If you must edit an active workflow, Jira creates a draft. Publish changes only after thorough review and testing.
Communicate Changes: Inform all affected users about upcoming workflow changes, and provide documentation or training if needed. Transparency reduces confusion and resistance.
Roll Out Gradually: If possible, apply changes to a pilot project or team first, gather feedback, and then roll out more broadly.
Leverage Jira’s Flexibility: Jira allows you to adjust workflows dynamically, so you can accommodate changes without major disruptions. Use features like board configuration and automation to adapt processes as needed.
Monitor and Iterate: After changes, monitor how the workflow performs and be ready to make further adjustments based on team feedback and metrics.

Articles:

Jira Workflows: Everything You Need to Know | Jira Guru

Jira workflows overview

Manage workflows and schemes

I hope the above information is useful and help you address your query.

Regards
Chitra Nagdeo

John Funk

Hmm, this sounds a LOT like mine except mine was written by me and not AI :-)

@Chitra Nagdeo - Please refrain from using AI strictly in your answers.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud