Epic Rule Workflow

[Prasanna N R]

Hi,

I am unable to add rule for transition in the workflow related to epic

[Hans Polder]

Hi @Prasanna N R ,

Welcome to the community!

We'll need a bit more information to help you properly. Can you maybe share some more context, and perhaps screenshots to get us started? What issues/errors are you running into? What have you tried already? :)

[Prasanna N R]

Hey @Hans Polder 

I am trying out jira for the first time. And exploring about workflows etc. 

Let's say I have few statusss A ,B and C. And issues I1, I2. 

I1 is created for E1 epic and I2 created for E2 Epic. Initially all tickets are in A status. I need to limit all tickets that are not created for E1 from going

A-x->B-x->C.

Where as tickets which are created for E1 can pass through 

A->B->C

Kindly Let me know if there is any gap

[Hans Polder]

Hi Prasanna,

Thanks for the clear explanation! So, if I understand correctly, you're trying to have one workflow for all I's (Issues) that are not Epics, but depending on the Epic they are child of, the workflow needs to be different.

While there might be (paid) plugins available that would help you achieve this out of the box, I believe this is achievable in Jira as well, but it requires some actions outside the workflow to work. However, keep in mind that while you are on the Free edition of Jira, some options listed below might be limited.

The way I would approach this:

1) Add an identifier on Epic level that states which type of Epic it is. You could add this in a new custom field, or as a Label. Keep in mind that labels can be somewhat error prone as anyone can add new labels or remove existing ones.

2) Create an automation rule that copies the value from the Epic to children (same custom field or label field as on the Epic itself)

3) In the workflow transitions for your Issues (so, the arrows going from A-X and from A-B, you can add conditions like "custom field X = Epic Type A" to ensure that the transitions will only be visible/available for the correct situations.

Alternative

Keep in mind though that usually, the way to differentiate workflows is through creating a new issue type. For each issue type, you can easily define a separate workflow without all the ifs and buts. However, depending on your use case/context it might not be applicable or usable.