Automation: Assign Epic's Component to new child Work Items

[Drew Clifton]

When I create a Work Item, I would like it to automatically "inherit" the Component of the Epic it belongs to.

BONUS:

I would also like sub-tasks to inherit the same Component (it could pull from it's grandparent Epic, or parent Work Item).

Thank you so much.

[Trudy Claspill]

Hello @Drew Clifton 

Welcome to the Atlassian community.

Have you tried to create this automation rule yet? If so, show us what you have so far and tell us what part is blocking you.

When would you want this inheritance to occur?

What would you expect to happen if an item's Components were manually changed?

For other factors to consider in your scenario, take a look at this excellent article by @Bill Sheboy 

Automation concepts – Sum or Synch Fields with Parent and Child Work Items 

[Bảo Phạm Gia]

You can do this with Jira Cloud Automation:
Work Items inherit Component from Epic
- Trigger: Issue Created
- Action: Edit issue 
Component = {{issue.epic.components}}
Sub-tasks inherit from Parent : {{parent.components}}
Optional fallback: if parent is empty, take from Epic:
{{parent.components}}
{{issue.epic.components}}

If you using Rovo (AI), just tell it:

Create an automation so new issues inherit Components from their Epic or Parent automatically.