How can I get subtasks to follow different workflows depending on parent issues.

Question

If the parent issue is a Story I want it to follow workflow #1.

If the parent issue is Task I want it to following workflow #2.

I have both workflows in a scheme with the type of workflow I want to use. Creating a separate subtask type introduces a lot of problems so I think I need to ditch that idea.

Any suggestions on how to accomplish this in Jira Cloud?

Iago Docando · Answer

you're right with "One issue type - one workflow" but check my workaround, maybe it is useful to you aswell.

Iago Docando · Answer

Every issue of a certain issue type will follow the same assigned workflow BUT there's a workaround for this using Jira Misc Workflow Extensions like Jimmy Van suggests. Maybe there are more options out there but this is the one I know and the one I've used.

Let's say you have workflow A and worflow B. You could create a new workflow combining both and then simply add a initial fork with two transitions, one pointing to each original workflow. Those transitions must have a condition set so if the condition is not met you can't advance the issue through that path. In this way the unwanted original workflow will be unreacheable.

In theory you could do this for any number of worflows you want to choose from but the more you have the more complicated resulting conjoined workflow you'll get.

Things to account for:

* beware of statuses that you can transition to from any status. They would be allways reacheable regardless of the initial branching.
* at least some automation tools that automatically set the status of an issue could set any of the statuses included in the conjoined workflow. The branching only prevents unwanted manual transitions.

Hope it helps.

Jimmy Van (GLiNTECH) · Answer

Have a look at Jira Misc Workflow Extensions. You can add validators for different JQL conditions.

I'd be keen to understand why you think a separate subtask type introduces problems though. Is it because filters will break? Users will need training with the new workflow, and it seems like a simpler solution long term.