How to copy the value of a custom field from Initiatives to Epics using automation for Jira.

[Luca Calderone]

Hi there,

We are looking at propagating the value of a Custom field from Initiatives to Epic and then down to Stories every time that field is populated or edited on the Epic.

We use Parent Link to connect Initiative - Epic and Epic link to connect Epic - Stories.

I am looking at using Automations, and currently struggling with the Rule to copy the value from Initiatives to Epics.

We'd then use a second simple Automation (which would be triggered by the first one) to propagate the same value down to the related Stories.

First Automation:

• When: Value changes for "custom field name"
• For JQL: Type = Epic <-- this would update all the Epics and not only the one/s in question.
• Then: Edit issue fields "custom field name"

Second automation:

• When: Value changes for "custom field name"
• For Stories
• Then: Edit issue fields "custom field name"

 Allow rule trigger

Thanks in advance!

[Walter Buggenhout · Accepted solution]

Hi @Luca Calderone,

Your automation rule is missing a branch, which tells it to update the child issues from your triggering issue.

The rule should look somewhat like this:

 

In the edit issue fields action, select the option copy from trigger issue. I've used assignee in this example, but you can obviously replace that with the custom field you want to sync.

Hope this helps!

[Luca Calderone]

Hi @Walter Buggenhoutthank you so much for your prompt response, it worked as expected and it triggered the second automation to pass the value down to the related Stories (connected via Epic Link). I really appreciated your help.

Have a great day and thanks a lot again.

Luca Calderone 

[Matthew Rochman]

Yes this works great. I will say on my automation, the 'edit issues field' copied the value from the parent issue and this works, but splitting hairs as I trust both work, practically and logically.

By the way, the key for me was doing a branch rule as above: "parent link" = {{issue.key}}

This boils it down to a small number of issues and the automation is lightweight and fast. 

nice solution