How to use Jira Automation to copy components from Epics to the issues within the Epic

[Holly Schomann]

I have tried using the answers from other posts on this topic, but those solutions are not working.  

I would like to use automation to copy the components of Epics to the children tickets (see below).  However, the automation keeps updating the epic.

I have moved the issues type condition and still no luck.

Holly

[Bill Sheboy · Accepted solution]

Hi @Holly Schomann 

When you want to edit an issue, automation use the scope at that location in the rule.  In your image, you show a branch on the epic/parent and so that is what gets edited.

If you want the epic's components copied to its children, you could try this:

• trigger: scheduled on JQL for any open (not completed) epics
• branch: on the stories/issues in the epic
  • conditions: as needed... such as not done, etc.
  • conditions: doesn't already contain the components you want to set
  • action: edit issue fields components, use the ... menu to select Copy From Parent Issue

Best regards,
Bill

[Holly Schomann]

Thanks Bill for your response. This is helpful. Can you include a visual, as I believe i have tried this as well.

I have the JQL searching for open epics with specific components.

I then just need all tickets in those epics to copy the components from the epic.  I still wasn't able to get it to work. 

If you could include a visual that would help me.

thanks so much

Holly

[Bill Sheboy]

Here you go, Holly...with some additional explanations about why it may not be working for you.

• The scheduled trigger uses JQL, such as this one I used to ignore some test components.  Change these as needed.

issueType=epic AND component IS NOT EMPTY AND component NOT IN ("ABC", "DEF")

• The scheduled trigger disables the option "Only include issues that have changed since the last time this rule executed"  You may want to re-enable this after the rule runs the first time to improve performance.
• The branch also disabled "Only include issues that have changed since the last time this rule executed" so changes to epics update children, even when they have not changed.
• The Edit Issue changes the Components field, selecting Copy Components from Epic issue, as I described earlier
• Also for that edit, there is a checkbox for Add to existing values. 
  • Leave that checked if you want the epic's components added, and
  • Clear it if you want the epic's components to replace values in the children

If that gives you problems, please post your rule image and the audit log from an execution.

[Holly Schomann]

Bill!! 

OMG..thank you so much!  It worked!  I had spent so many hours on this. You are my hero!!

Not only did you save me from spending more time on this, but you also helped me look like a rockstar to my team.

I really can't thank you enough!

Hope that you have a good weekend.

My sincerest thanks,

Holly

[Bill Sheboy]

I am glad to learn that helped you, Holly.  I hope you have a great weekend!

__Bill

[Ramonde Zrihen]

@Bill Sheboy : hi ! can you please help in copy components from one project to another using Automation in cloud ?

thanks !

[Bill Sheboy]

Hi @Ramonde Zrihen 

First thing, as your question seems a bit different from this thread, I recommend creating a new question and then linking to this one for reference.  That will get the most visibility so the community can help.  Otherwise only the people following this thread will see it.

Next, components are configured at a project level, and so you could

• manually re-create the components,
• use a marketplace addon to manage/copy components, or
• use an automation rule which calls the REST API with a web request to Get Project Components, and then use an advanced branch to iterate over the results to call another REST API to Create Component one by one

The approach you select may depend upon your ability to purchase an addon, and how often you need this and other constraints (e.g. what happens when components change between projects).

Kind regards,
Bill

[Ramonde Zrihen]

@[deleted] : thank you for your quick reply ! i thought there might be an easier solution rather "managing" it while edit / delete etc'... /buying add on / update manually

thank you in advanced !
Cheers !!
Ramonde

[justyna oltarzewska]

Hello, I tried to replicate this automation in my project and it doesn´t work, do you have any Idea why? Maybe it is about JQL ... I don´t know what should I put inthere, Attached  screenshots

[Bill Sheboy]

Hi @justyna oltarzewska -- Welcome to the Atlassian Community!

As this is a very old thread, I recommend creating a new question, and perhaps including a link to this one.  That will ensure the maximum number of people see it to offer suggestions.  Otherwise, only people following this older thread will see it.

When you post your question, please include images of the complete rule, the audit log details showing the rule execution, and explain what is not working as expected.

Until we see your new question...

I note your rule trigger has the option selected "Only include issues that have changed since the last time this rule executed".  And so many issues may be excluded from the rule processing them.

And, the trigger JQL just checks the component field is empty.  Do you also want this rule to ignore completed issues?

Kind regards,
Bill

[Julien Peyrade _ Elements]

Hello @Holly Schomann 

Another solution would be to use an add-on.

I'm the Product Manager of Elements Copy & Sync, which lets you do just want your are requesting. You can copy the Components to the issues under the Epic when you create them, and keep them synchronised afterward.

Don't hesitate to ask if you have any question.

Kind regards,

Julien