Automation for Jira - For Epic (parent) not working

[Dax Tulpenventer]

Hi,

I've read multiple questions and articles on how to automatically change the status of an epic depending on the status of the task(s) it contains. In this case I only have tasks, no stories. I just can't seem to figure out how to get it done.

This is my rule:

As I understand this is what should happen:
1) An issue is transitioned to "Actief"
2) Check if it's a Task
3) We switch from the task to the Epic it's in
4) The Epic transitions to "Actief"

The log just tells me it passed the first check (step 2) and there's nothing else noted. Only the status "no actions performed".

It seems like step 3), switching to the Epic, doesn't do anything at all. It feels like a bug to me but I'm probably doing something wrong. Could someone please explain? Thanks for your response.

[Petter Gonçalves · Accepted solution]

Hello @Dax Tulpenventer

Thank you for reaching out.

Analyzing the steps of your Automation rule, it seems that everything is properly configured to transition the linked Epics when the related child tasks are transitioned.

That being said, I think the problem might be occurring by one of the following reasons:

- Next-gen projects use a different mechanism of Epic-child link, which the Automation rules are not able to recognize yet, although we have the following feature request to make it work:

Setting epic link in Next-gen projects is broken in cloud

If you are using Next-gen, I'm afraid we don't have a way to make it work with Next-gen projects at this moment, so I recommend you keep an eye in the feature request and move your issues to a Classic project.

If you are using a Classic Jira project:

1 - Doublecheck if the task you used to test is properly linked as an Epic child to an Epic and not as a default link of Jira issues.

2 - Check if the Epic workflow (If it uses a different workflow than the task) is properly configured to allow the transition to the status "ACTIEF" and does not have any conditions or validators that might be blocking the transition. 

Let us know if the steps above helped.

[Dax Tulpenventer]

Thanks, it was indeed because I was using a next-gen project.

[Ans Hassel]

Thanks I am after the exact same functionality, and was scratching my head ... good to know hat what I'm doing is correct but just not working yet for Next Gen