Automatically change an epic status when its child issue in a different jira project is done

[Heba Rezk]

Hi!

I have this case i need to create a jira automation rule for:

3 projects

Project A: Epics

Project B: tasks for team 1 and the parent epic is in Project A

Project C: tasks for team 2 and the parent epic is in Project A

now an epic in jira project A consists of tasks from project B, and C. I need the Epic to transition in Project A to a following status when a task in Project B key is done

example

Task of Project B moves to done >> change epic status in project A to : ready for team C

[Trudy P Claspill · Accepted solution]

Hello @Heba Rezk 

Should the Epic be transitioned if any child issue in Project B is transitioned to Done? Can other child issues in Project B be in any other status?

What if the child issue in Project B reverts to a not-Done status, and no other child issues in Project B are in a Done status?

Does it matter what status the Epic is in when this occurs?

This will require creating a multiple-project rule from the Global Automation page. The scope of the rule must identify Project A and Project B. If the status of the child issues in project C are irrelevant then that project doesn't need to be included in the scope.

[Heba Rezk]

Thanks @Trudy Claspill for your repsonse.

Yes, as each team's jira project contributes to the Epic execution with only one task, so when Project B task is done, the epic transitions, then when project C task is done, the epic transitions to the following status, and so forth till the epic itself is done.

I create a global rule that is for project A and B, but i could not define the details that when the task is done in Project B, its epic in Project A should transitions to the specific status i want.

[Trudy P Claspill]

Please show us the rule you have constructed.

Could an issue in Project B have a parent Epic that is also in Project B, and if so would you want the rule to run for that scenario also?

The basic structure would be:

[Heba Rezk]

It worked @Trudy P Claspill !! thanks a lot.