Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Copy field value from Epic to child issue with automation


There are couple fields in child issues that mostly match the parent issue, but sometimes need to be changed. For easy implementing I would like to copy the Epic values upon creating the child issue. I tried using 'Automation' in different configurations but I can't get it to work. It say's 'Succes' but the fields in the new issue don't reflect the fields in the Epic.

Schermafbeelding 2020-07-02 om 11.40.55.png


This is the current exported rule:


Schermafbeelding 2020-07-06 om 18.18.16.png

Thank you for taking your time to help me with this issue!

3 answers

1 accepted

5 votes
Answer accepted

Hi @Huey van Zijl 

Would you please post images of your rule definition?  That will help the community try to answer your question. 

Your custom fields are different from those defined in other people's instances, so importing the rule's JSON may not help others understand your rule.

Best regards,


Hi Bill,

Thank you so much for replying so soon! I've updated the original post. :)

- Huey

Hi Huey,

Thanks for the additional information.  Three next steps to try:

  • After the trigger, add a condition to test if there is an epic link.  This could be a timing issue, or perhaps the issue doesn't have an epic.
  • Your image shows the rule in draft status.  Is that just from viewing it, or are there un-published changes to save/publish?
  • Next, before your copy action, add a branch on the epic to add a comment including the parent's values of those fields.  That will confirm they are indeed what you expect prior to the copy.

Best regards,


Hi @Huey van Zijl 

An update: another community member saw a similar issue with the edit/copy not working.  They solved that by adding a re-fetch action to solve a potential timing problem where the created issue does not yet have the parent link.

So, your updated rule would be:

  • Trigger: issue created
  • Action: re-fetch the issue
  • Condition: confirm the issue has an epic link (not empty)
  • Action: edit issue to copy the parent epic's fields
Like # people like this

Hi @Bill Sheboy ,


Thank you so much for helping me, your advice did the trick! For anyone searching the forums here is my implemented solution:


20200707 Jira automation copy epic values to new child issue.PNG

Tip: be sure to configure the last step 'Then: Edit issue fields" correctly by telling it to copy from epic. :) 

Like # people like this

Just wanted to say thanks to @Bill Sheboy for this answer.  Worked perfectly first time and saved me the time having to figure it out

Like Bill Sheboy likes this

I have this automation running and it works when an issue is created; however is there a way to get this to trigger when the field value changes on the Epic and it copies the the new field value to all child issues (tasks/stories)?Screen Shot 2021-12-15 at 12.05.16 PM.png

Hi @Brellison -- Welcome to the Atlassian Community!

First thing: please consider creating a new question, and perhaps linking to related ones.  That will ensure more people see it...only the people currently following this thread will see it otherwise.

On to your questions...

The rule you show is triggered on a field value change, not issue create.  Are you certain that triggers on create as you noted?

Next, you should be able to detect the change in the epic and then copy that down to its child issues.  For example:

  • trigger: field changes
  • condition: issue type is epic
  • branch: on the epic's child issues
    • action: edit the field, copying from the trigger issue

Please also see the template library for other example rules like this:

Kind regards,

Like # people like this

Thanks for your help Bill! Your solution helped.


For clarification, I had the original rule in this thread running fine, but found a limitation in it that when the Epic's fields were updated, the existing issues' fields did not update to reflect the new value. But the automation you provided me fixes that.

Like Bill Sheboy likes this

Hi ,

I have tried the same .but it is copying from parent to child .but not child to grand child.any suggestions?

Hi @Aarohi 

Please consider creating a new question, and perhaps linking to related ones.  That will ensure more people see it...only the people currently following this thread will see it otherwise.

Regarding what you asked about...

Are you using Jira Cloud or Server/Data Center version?

If on Cloud, what is your project type: Company-managed or Team-managed?

When you note you tried the same thing, what do you mean?  Would you please post images of your complete rule and audit log details, showing the execution which does not work as you expect?  That will provide context for the community to offer help.  Thanks!

Kind regards,

I am using jira cloud and Project type is Company managed

Thanks @Aarohi 

Currently, nesting of branches is not possible, so you would need 2 rules.  The only differences between the rules are the conditions and the branches.

  1. When label changes for an epic issue type, copy the values to the child issues (story/task/bug issue types)
  2. When label changes for a child issue type, copy the values to the grandchildren (subtask issue types)

Rule #1 can trigger rule #2, so in the detail settings for Rule #2 you may enable the "Allow Rule Trigger" option to make this work.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events