Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

Recognition

  • Give kudos
  • My kudos

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

"Can" vs "Should" I use multiple workflows for different issue types.

I've search for and seen pages that discuss Jira's ability to have multiple workflows for different issue types. And it seems so obvious from an operational standpoint that a team would have something more like "Backlog=>Selected For Development=>In Development=>Ready For User Acceptance Testing=>Ready For Deployment=>Feature Complete" for new features and enhancements and something more like "Open=>In Progress=>Ready to Deploy=>Fixed" for defects.

 

I know from those other pages that Jira "can" do this. But are there any caveats or gotchas that occur from doing so? Is there a best practice respecting this?

 

1 answer

Hello @brandidantzler

Welcome to Atlassian Community!

Indeed, it is possible to configure different workflows for a single project, each of them relating to different issue types. The whole set of workflows defined to a specific project for different issue types is called a Workflow Scheme, as you can see in the documentation below:

Configuring workflow schemes 

In fact, most Jira Service Desk templates and even some Jira software templates work with multiple workflows. Its indeed a good option when you have different necessities/steps for multiple departments.

The main consequences and relevant points about this approach are:

1 - When you have a single workflow for your project, it is possible to change the issue type of your issues by simply clicking in the field at the issue view. Once your issue types are not configured with a common workflow, you will be requested to move your issues when you click to update its issue type, since they will be migrating from one workflow to another.

This is really not a big deal, just a small difference of three extra steps you'll need to do in order to change the issue type of any issues.

2 - You will not be able to use simplified workflows in your Jira board. This is also not a big deal, just make sure you have properly mapped all the new statuses you created under your board settings > Columns

3 - Jira default workflows are pre-configured with several properties and post functions to make sure they work properly. That being said, I strongly recommend you to make copies of already existing workflows and customize it, instead of creating a new workflow from zero. This will ensure your new workflows will be functional as the one you have today.

Let us know if you have any questions.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence Cloud

Share your Confluence Cloud experience for a chance to win $500!

Take our 5-minute survey to win a $500 Visa gift card! Are you currently using Confluence Cloud? We want to hear from you! Fill out this quick survey about your Confluence Cloud experience so we ...

194 views 2 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you