Select child and sub child on an automation branch to edit sub-tasks

[Inés Ferrer]

Hi there,

I built an automation wether I create and Epic and from that Epic I trigger manually the automation.

This automation creates a tree full of tasks (childs from epic) and subtasks (subchilds - child from tasks).

The subtasks are not copying some fields from the task. I tried to add a last branch "for all created issues" and copy those fields from the epic (tried with "copy from parent/trigger issue/current/epic issue"), but it didn't work.

I hope if any of you could help me.

[Inés Ferrer]

Hi,

The automation creates several tasks copying fields from the epic. Then, for each task, some sub-tasks are created but they are not copying all the fields from the parent, although they are available.

Then, at the end of the automation there is a last branch which edits fields for all created issues, but the subtasks don't get these fields updated.

I am also attaching a screenshot of the task and subtask fields setting, proving all fields are available in both issue type.

Hope someone can help.

Best regards,

[Inés Ferrer]

Hi,

The automation creates several tasks copying fields from the epic. Then, for each task, some sub-tasks are created but they are not copying all the fields from the parent, although they are available.

Then, at the end of the automation there is a last branch which edits fields for all created issues, but the subtasks don't get these fields updated.

I am also attaching a screenshot of the task and subtask fields setting, proving all fields are available in both issue type.

Hope someone can help.

Best regards,

[Trudy Claspill]

Hello @Inés Ferrer 

Welcome to the Atlassian community.

When asking for help with an Automation rule, it will help us to help you if you provide the following:

- screen images that show your entire rule

- screen images that show the details of the steps where you are trying to set the data

- the details in the Audit Log for the rule execution

[Inés Ferrer]

Hi, added some screenshots

Thank you

[Trudy Claspill]

Hello @Inés Ferrer 

Unfortunately branches do not necessarily execute in the sequential order in which they appear in a rule. Refer to

https://confluence.atlassian.com/jirakb/in-the-automation-parallel-execution-of-the-branches-to-main-thread-can-produce-incorrect-unexpected-outcome-1115147731.html

Subsequently, you second branch to update all issues created in the rule may be executing at the same time as the branch that creates subtasks. The structure is not a reliable way to ensure the issues created in the first branch get updated.

There are a couple of alternatives.

1. In the same actions where you are creating the issues and creating the subtasks, set the fields that you want to copy.

2. Move the actions of the second branch to a separate rule. In the first rule you could add a label or other identifying piece of information to the newly created issues and use that as a condition in the second rule to determine that you need to copy data from a parent issue.

In addition, the rule may have some difficulty copying data to a sub-task when you say copy from the "Epic Issue". Sub-tasks don't have a direct relationship to an Epic. They have only an indirect relationship to the Epic through the issue that is the child of the Epic and the parent of the subtask. You may need to instead use Copy From Parent Issue, or Copy From Trigger Issue (if you try to set the fields in the Create Issue action in the original rule.)