nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation: Parent-child issues Transition

Amy Chang_299cvs

Hi,

Does anyone know how to do the below scenarios:

1. When the 1st Task transits from Priority to WIP, it automatically transits its parent to In Progress.

2. When the last child issue moves to Done, close the whole Epic.

In our project, we have 3 hierarchies - Initiative (1st ), Epic (2nd), and Task (3rd); their relationship can be referred to in the attachment below.

The problem I encountered is:

When one of the Epic is closed by the automation (Scenario 2), the Initiative will be affected by this automation and transit itself to Done even if it has the Epic (child) in In Progress status.

How can I avoid this problem, and what adjustments can I make to my automation?

Thanks!

Accepted answers

John Funk

Hi Amy,

Add a Condition in the first rule above right after the trigger and before the Branch to check if the Issue Type = Epic

All comments

John Funk

Hi Amy,

Add a Condition in the first rule above right after the trigger and before the Branch to check if the Issue Type = Epic

Bill Sheboy

Hi @Amy Chang

Agreeing with John's suggestion, and...some questions to clarify the use case:

Do you want the Initiatives to also update for those scenarios, based on changes to their child Epics?

For either of your rules, have you enabled the "Allow Rule Trigger" setting in the rule details at the top? Enabling this option allow the action of a rule to trigger the same, or other rules. That may not be desired if you do not want the Initiatives to automatically update.

Kind regards,
Bill

Amy Chang_299cvs

Hi @John Funk and @Bill Sheboy

Thank you for your suggestions.

Yes, it would be good if the automation could update the Initiative.

I made the automation for the Initiative (the same rule as the above attachment) but set it as the global rule. The reason is that in our Jira, each Project = each department, so we need a top-level type (Initiative) to include all the related tasks. The Initiative contains Epics from different projects, so I encountered difficulties with the automation. I'm not sure whether the automation didn't work perfectly because of this.

Moreover, I didn't select the "Allow Rule Trigger".

John Funk

So with those changes, is it working now?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud