Different workflows for change requests

Hello there,


we currently are in the process of evaluating of switching to JSD, but we found an not so nice block in the road.

We have a quite large organisation where we have within a project several change requests. These requests might also have different workflows. Are we right to assume, that different workflows are not applicable in JSD for a change request? We really do want to stay with the concept of issue type.

Are there any best practices how to solve that problem?



4 answers

1 accepted

2 votes
Answer accepted

As Thomas said you need different issuetypes :

"Change Request for A", "Change Request for B", ...

Be creative :-)

We will probably go with that route. Most clean solution in my opinion. Thanks for all the input :)

2 votes
Thomas Schlegel Community Champion Dec 15, 2017

Hi Alexander,

if you need different workflows in the same project, you need different issue types.

But in different projects, the workflows for the issue type "Change Request" can be different.

After Creating different Issue Types All the Issue are migrated to another Board created.

Or maybe you could try something like this and split your workflow path:


My personal Best Practice, with all my customer,

  1. Validate if is not possible to create more than one type of Change Request. 
    • If yes, do it, it will be easier to manage
  2. If you really need to have more than workflow, you need to create only 1 Jira workflow that implement the 2 workflows.
    • To do that,
      • You need to find a way to segregate your 2 workflows
        • Habitually, you use a select field (1 option), a Checkbox or a radio button Field
      • You need to have a minimum of 1 status in commun between the 2 workflows
      • You have 1 limit, you cant have a transition having the same name but different behavior between 2 statuses
    • To implement the 2 workflows in the same Jira Workflow, add a Condition to each of your transition of type "Value Field" (or like this one). Using that you could limit the transition and the statuses available on a workflow depending on a SubType like Customfield.

It's not perfect, but it's working fine.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 13, 2019 in Jira Service Desk

What's new in Jira Service Desk Server: Introducing 4.0 & more - Feb 2019

Hello Atlassian Community!  I'm Teresa, the Product Marketing Manager   for Jira Service Desk Server at Atlassian. I'm excited to announce two exciting releases for Jira Service De...

393 views 1 1
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you