Update epic status according to child issues

[Assem E]

In epic we have many issues in different types. It is necessary to automate Epic status regarding these issues statuses. For example, if there is QA task in progress, Epic should be in Testing status even if there are other tasks of analysis and development. When QA task is done6 epic should return to Dev status since actual child issues are in Development progress

should be implemented in Jira Data Center

[arielei]

Hey @Assem E 

You can create the following automation:

1. Trigger: 

• Set the trigger to "Issue transitioned".
• Specify the child issue type (e.g., Story, Task).
• Define the status transition that should trigger the automation (e.g., from "In Progress" to "Done").

2. Condition: 

• Use a "Related issues condition".
• Select the "Epic" as the parent issue.
• Choose "Stories (or other issues in the Epic)" as the related issues.
• Add a condition to check if all related issues are in the desired status (e.g., "Done").

3. Action: 

• Add an "Edit Issue" action.
• Select the "Epic" as the issue to edit.
• Choose the field to update (e.g., "Status").
• Set the desired status for the Epic (e.g., "Done").
  
  

Example:

Let's say you want to automatically move an Epic to "Done" when all of its stories are moved to "Done". 

1. Trigger: When a story is transitioned to "Done".
2. Condition: If all stories related to the Epic are in "Done" status.
3. Action: Transition the Epic to the "Done" status.

[Assem E]

Thank you for answer

But what I need is little bit different. I want scheduled automation rules that checks all epics (except done) and their child issues, and change the status of an epic to actual status according to child issue type

[Yogesh Mude]

@Assem E  May i ask you why you want to use scheduler? as mentioned by @arielei you can trigger the issue transition event and verify the child is moving to the next state and based on the Epic also follows the same instead unnecessary adding the scheduler and running it to all the time.

So, lets assume if you run scheduler every hour and the epic is moving to the next state based on the child then there will be a huge gap in syncing with the team.

Its best to trigger the issue transition event whenever the child is move and based on that the parent also move.

[Assem E]

Users want to automate in such format: for example, epic has 1 QA task and 2 Development task, if QA task is in progress, Epic should be in Testing status. When QA task is done, but Developments are in progress Epic should go back to Dev status. If I trigger on issue transitions, it wont be in actual status since there are could be many child issues

[Yogesh Mude]

In this case you can check the child issue state Or add the conditions if all child issues are done then only should moved.

[Staffan Redelius]

Hi @Assem E 

This can be done using automation as described by @arielei  but it seems a bit confusing since the Epic status will be based on the last updated child.  The Epic is only a container of  child issues and the status for the whole Epic hasn't reached i.e QA. Only one of many child issues.

A more common approach is to have generic statuses for the Epic like "Open", "In progress" "Done" The Epic can be moved to "In progress" when the first child issues reaches "In development" or be moved to "Done" when all child isues are closed using autmation in the same fashion.

One other note is that you need to allow transitions to all affected statuses in the Epic workflow to not make the automation logic unnecessary complicated.