Automation - Add parent component to any child issues

[Fitzpatrick, Oliver]

Hi,

I would like to add any component that is added to a parent issue automatically to any child issues that are created.

E.g.

Epic 1 has component x added

User created user story 1.1 underneath Epic 1.

Automation runs to add component x automatically.

Is this possible?

Thanks

[Alisa Zamaraeva]

Hi @Fitzpatrick, Oliver 

If you need to copy value from parent/epic issue when child issue is created, then you rule can be like this:

1. Trigger - Issue created

2. Any condition you like

3. Action - Edit fields with copy value from <whatever you choose>

If you want to keep components for all child issues up-to-date when epic components are updated, you can create one more rule that may look like this:

Hope this helps!

[Fitzpatrick, Oliver]

Hi @Alisa Zamaraeva  Thank you for your response. I'm not sure whether you have seen my reply to another response. Would this work? I think it's similar to what you proposed, but has a different branch rul

[Alisa Zamaraeva]

@Fitzpatrick, Oliver I'm not sure it will work, since the logic behind it would be like this:

When issue is created, automation checks if the created issue has the component and if yes, for sub-tasks of this created issue (which most certainly don't exist yet) edits fields. In other words, the rule runs and checks conditions against the issue that triggered it.

[Craig Nodwell]

Hi @Fitzpatrick, Oliver have a review of this page.

[Fitzpatrick, Oliver]

Thanks Craig. I'm not sure it was exactly what I was looking for, but did give me inspiration for this:

Would this work?

The only issue I see is that it only runs when a new issue is created. What happens when an issue is created on Day 1 and then a sub-issue is created on Day 2 for example. Would this still run?