Workflow transitions depending on issue types

I've got a JIRA workflow that needs to be different depending on the issue type.

So after creation, it needs to go to a "For Verification" state if it is a bug, and to "To Do" if it's anything other than a bug.

I cannot have more than one transition from "Create" and there is nothing (I'm aware of) that allows to move the issue to another state automatically if certain criteria are met (I wanted to just forward everything that is not a bug to "To Do" as soon as it's put in "For Verification".

So the workflow is: Create/[Verification(if bug)]/To Do. Only bugs shall be verified anything else needs to skip that step. How can I achieve that?

The only solution I have now is to use two workflows but I don't want that - it's too much work maintaining two workflows.

6 answers

1 accepted

Accepted Answer
0 votes

Use Auto Transition Listener and transition issues of all other types to ToDo as soon as they are put in 'For Verification'.

https://studio.plugins.atlassian.com/wiki/display/JTOOL/Auto+Transition+Listener

That is what JIRA is meant for.

Define two workflows, one for bug and one for others. Configure your workflow scheme and associate the issue type with the workflow. Read https://confluence.atlassian.com/display/JIRA/Configuring+Workflow+Schemes

That's what I have. But when I'm changing the workflow I have to make changes to both of them. It's just this tiny difference and I'm more of the DRY type of a guy for obvious reasons.

0 votes
Ahmad Danial Atlassian Team Feb 10, 2013

Hey there, Elbe.

Sounds like you require quite an extensive customization for the workflow. I don't think JIRA has the ability to decide whether an Issue Type can determine the transition of the workflow. Having that said, can you try to look into the following plugin that might be able to offer what you are looking for:

https://marketplace.atlassian.com/plugins/com.innovalog.jmwe.jira-misc-workflow-extensions

Else, you can try to seek help from the Atlassian Experts to see whether they are able to advice you on this matter:

http://www.atlassian.com/resources/experts#find-an-expert

Warm regards,

Danial

0 votes

Definitely a case for two workflows.

You could think about messing around with a listener to perform a second transition, or have two transitions and write a condition that says "if issue-type X then allow/disallow this transition", but separate workflows require no code and that's pretty much what workflow-by-issuetype is for.

You can also use OSWorkflow's Conditional Result feature by editing your workflow XML directly. This is documented at https://innovalog.atlassian.net/wiki/display/JMWE/JIRA+Misc+Workflow+Extensions+Documentation (look for a large green box)

Old question, but we addressed similar need with Scriptrunner plugin and the fast-track transition post function.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

21,506 views 2 7
Join discussion

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