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; } } }

Propagate custom filed value on Epic child items

Vasilisa Yermakova

Hello!

I'm trying to create an automation that will set the value of a custom field to the same value as their parent Epic.

So far I was able to make it work only for already existing items within Epic, but cannot make it work to set the value for newly added child items or items added outside of the current Epic.

Please see 2 screenshots with the automations I tried.

I believe the problem is that when I create a task even using "Add a child issue" for the specific Epic, it doesn't relate to any parent/Epic yet so it cannot understand where to take the value from. This is how I understand the error message shown in audit log (see attached).

And only after I perform some changes on child item it gets the value from the parent Epic.

Please let me know how should I improve these automations to make them work correctly. I believe this should be a common use case but unfortunately I wasn't able to find some similar solutions.

Accepted answers

All comments

David Leal_28ge8x

Please the details of the Edit issue field and also what exactly you want to achieve with the rule, it is not clear to me from your question. Thanks.

Vasilisa Yermakova

sure, thank you

I tried both options to set "Issue to copy value from" as Epic issue and Parent issue.

For the first automation that works it is set to "Epic issue".

Vasilisa Yermakova

From the rule I want to achieve that all child items inside the Epic got the same value for "test field" as it is for the Epic.

And the rule should be applied no matter if they:

- were inside this Epic before,

- were just added from backlog or from another Epic;

- or were just created by clicking "Add a child issue" right under that Epic

I hope it makes clear what I'm trying to achieve.

Boldizsár Vermes

@Vasilisa Yermakova, try using Value changes for: parent as a trigger instead of when an issue is created/updated. This will result in starting the automation only in case of a known epic.

I suggest creating a fallback option for issues that does not have an epic to clear the field value of them.

Vasilisa Yermakova

hi @Boldizsár Vermes

thanks a lot for your answer.

I was actually trying to use this trigger, but I didn't understand much its logic.

So the fact is that it works in cases when issue was created in backlog and then added to the Epic -> it works.

but in case if I try to create a new issue right under the Epic by using "add a child issue" button, the automation fails with the error in logs that I shared above.

I thought that newly created issue should be triggered as well, but it never happened.

What would be your recommendation for me to try next?

I'm new to automation and would highly appreciate any help!

Vasilisa Yermakova

hi @David Leal

I'll just ping you in case you don't get the notifications about new answers, thank you

Boldizsár Vermes

An automation rule of mine that sets a field when the issue is created or later the epic is changed would be as simple as the image shows:

Vasilisa Yermakova

@Boldizsár Vermes this is so strange as I don't know what I can be doing wrongly..

I removed additional conditions to keep the rule as simple as it is on your sample,

but still no success with items created within the Epic - rule always fails.

And even for the other case when I link items to the Epic created outside of it - rule executes twice, where first execution always fails but the second works.

p.s. In all cases the rule tries to execute twice. does it works the same for you?