Inheriting Component from Epic to Children when issues are created under Parent Epic

[AnthonioD]

Inheriting Component from Epic to Children when issues are created under Parent Epic

[Bill Sheboy]

Hi @AnthonioD 

Yes, and...to the suggestions from @Florian Bonniec 

Please consider there are many cases to handle a field synch between parent / child work items.  Based upon the level of accuracy and frequency of updates, this will require one-to-many automation rules.  To learn more, please see this article I wrote on field synch / sum scenarios:

https://community.atlassian.com/forums/Automation-articles/Automation-concepts-Sum-or-Synch-Fields-with-Parent-and-Child/ba-p/3162890

Kind regards,
Bill

[Florian Bonniec]

Hi @AnthonioD 

Have you try automation ?

I would trigger it on Field Value change Parent instead of issue created, just in case you assign the parent to the issue later.

So trigger: Value Change (Parent) or Issue Created

Condition: Parent exist

Action: Edit Work Item, Component Copy From Parent.

Regards