Copying fields Data from Epic to Parent and Sub-Tasks for Existing Tickets

[Lakshmi CH]

Hi Team,

Is there an option to sync field data from an Epic to its related Parent and Sub-Tasks for existing tickets?

I set up an automation using JMWE, but it only works for newly created Jira tickets. I need a solution to copy a specific field (for example, "RDS Team") from the Epic to its related Story and Bug issue types, as well as their related Sub-Tasks. I have a built-in script for ScriptRunner, but I don't think it addresses my scenario. Are there any other options to achieve this?

[Ram Kumar Aravindakshan _Adaptavist_]

Hi @Lakshmi CH

Could you elaborate a little more on the field type that you intend to sync with the Epic and its Parent issue?

Also, when do you want the sync to take place? Is it when the Epic is created or when a new issue is added to the Epic?

I am looking forward to your feedback and clarification.

Thank you and Kind regards,
Ram

[Lakshmi CH]

Hi @Ram Kumar Aravindakshan _Adaptavist_ ,

Thank you so much for your response. 

We recently added a post function in JMWE that copies the value of the "DS Solution Team" field from the Epic to the Story, and then to the Subtask -> This is working, and copying fields from Epic -> Story -> Sub-task.

To add this field value to an existing ticket, note that the value differs, making bulk changes unfeasible. The post function is only applicable to newly created tickets.

[Ram Kumar Aravindakshan _Adaptavist_]

Hi @Lakshmi CH

When you use Post-Functions, it will only work when the Issue transitions to a particular status.

After reading your last comment, I assume that you want this to trigger on the Create transition, which is why only when new issues are create it is able to work and not on already existing issues. Please clarify. 

An alternative I can suggest is to use a Scripted Field to copy the value from the Epic to the Story, Sub-task, etc.

If the Scripted Field would be fine, let me know, and I will try to provide an example.

I am looking forward to your feedback and clarification.

Thank you and Kind regards,

Ram

[Lakshmi CH]

Hi @Ram Kumar Aravindakshan _Adaptavist_ ,

Thank you for your quick response.

Sure, please provide an example so I can see how to adjust it in the existing tickets.

[Gizem Gökçe _OBSS_]

Hello @Lakshmi CH ,

Trying to make this work with automation rules or scripts can quickly turn into a complex, high-maintenance setup — and even then, it often won’t handle existing issues the way you need.

If you are open using a 3rd party app, we built Field Sync exactly for this kind of scenario. It can automatically copy field values (like your RDS Team field) from an Epic to its linked issues such as Stories, Bugs, and Sub-Tasks — and it works not only for new issues but also for existing ones. With the Sync Existing Issues feature, you can bulk-update all related issues in just a few clicks.

You can set up multiple listeners, choose which fields to sync, decide the direction, and cascade updates from the Epic all the way down to its children.

Disclaimer: I work for OBSS, the developer of Field Sync.

Learn more here: Field Sync on Atlassian Marketplace

Best Regards,

Gizem

[Cristiano Alves -Appfire-]

Hello @Lakshmi CH 

I'm Cristiano, with the Appfire team.

Have you tried saving the automation as an Post-Function and schedule it? 
I'm gonna leave an script option for Power Scripts below, as well as an link to contact AppFire Support, which also addresses JMWE

The Script using Power Scripts - Jira Workflow Automation.

With the following scripts (which were generated from templates that the app offer)

if(!isNull(parent)) {
customfield_10158 = parent.customfield_10158;
}
string[] subtasks = subtasks(key);
for(string subtask in subtasks) {
%subtask%.customfield_10158 = key.customfield_10158;
}

Then you may easily set up as an automation or an post function for a custom status and just run it or schedule it, the template window really helps with that, as per follow:

here is the link for the Appfire Support Team, you may ask them either about JMWE or Power Scripts.

Regards,

[Mohanraj Thangamuthu]

Hello, Good day. You can create a scheduled automation rule to copy the value from Epic to child issues. Then a second scheduled rule to copy the value from child to sub-task type. Once all issue are in sync, then you continue using JMWE for new work items. Thanks

[Lakshmi CH]

Hi @Mohanraj Thangamuthu ,

Do you have any sample one how to do with the scheduled automation ?

[Mohanraj Thangamuthu]

Hello, Good day. You can try the following automation rule.