How do I copy the component from a Parent/Epic to all tickets I create within it (upon creation)

[John McLoone]

I will be using components to group my epics in to larger sets. I will be using components as swim lanes and have setup the queries for that.

What I need to do now is ensure that when a story/task etc is created under an epic that it has the same component. All epics will only have a single component.

It would also be great if it would add the correct component when ever an already created story/task/bug etc (with no component) is linked to an epic with a component.

[Trudy Claspill · Accepted solution]

Hello @John McLoone 

Welcome to the Atlassian community.

You can do that with Automation Rules.

This rule will copy the Components from the parent Epic to the child issue when a new child is created and simultaneously added to the Epic, when a child issue is moved from one Epic to another, and when an issue that previously had no parent Epic is added to an Epic. Any Component value already in the child issue will be overwritten in this process.

[John McLoone]

You're a star, thank you!

[bhankinson]

This is exactly what I was looking for too thank you!

[Melanie Whyte]

This is exactly what I am after as well. It doesn't seem to be working for me though.

I think that i have the same set up you suggested in the automation. So i'm not sure why not.   Do you have ay ideas what I might be missing?

Thanks

[bhankinson]

Looks like there is a typo in your JQL 
Try that

[Velizar.Velizarov]

This solution doesn't work for me. I need to copy component/s from Phase(Parent) to the Epic(Child) in Automation when the Epic is created.

Thanks.

[Trudy Claspill]

Hello @Velizar.Velizarov 

Welcome to the Atlassian community.

Given that this post has an accepted answer, and you are saying the solution does not work for you, please create a new Question post by clicking the Ask a question button in the menu bar at the top of this page.

In your new post provide 

1. Identify the type of project you are using (Team Managed or Company Managed, Software or Business or Service Management). Get that information from the View All Projects page under the projects menu.
2. A screen image showing the Issue Type Hierarchy for your instance (because you referenced an issue type that you say is a parent to the Epic issue type).
3. A screen image that shows your entire rule.
4. Screen images that show the details of each step in the rule.
5. A screen image that shows the entire Audit Log output for a time when the rule executed and the results were not what you expected.
6. Screen images showing the Components field of the parent and child issues.
7. A link to this current post, if you think it is relevant to your issue.