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

Autofill field 'customer' for child issues, if epic has 'customer' field filled

I am looking for an automation that can help cascade the 'customer' field value to all the child issues once this field is filled in an epic. Also if an epic has 'customer' field filled, any child issues created should have the same customer field henceforth. I went through the options available in the JIRA automation, however this does not seem to be a simple one. Please assist. 

1 answer

1 accepted

3 votes
Answer accepted

Hi Mohsin!

What kind of field is your 'customer' field? Is it an user field? A text or email field?

@Bill Sheboy previously offered an answer that is very similar to your request:

To quote him:

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

You would just need to specify the 'customer' field is the one you're triggering off of.

If you have problems, it's best to take a screenshot of your rule and add it here.

Hi @Mohsin Khan

@Darryl Leeanswer is perfect for this. When you update that field branch for epic children and edit the field using the value from the trigger.


Will this work? I created automation based on above instruction:



Darryl Lee Community Leader Jun 10, 2022

That looks right to me. Did you test it? 

The other thing you might want to do is decide whether it should be scoped to a single project, multiple projects, or to all projects. You would set that in the Rule details, and if you select multiple or all projects, you may be limited by the number of rule executions based on your plan type:

Hello Darryl. It works wonders for me. Thanks ever so much. Just one help. Currently it is working only on any stories that I create under the epic. But I want it to work on even sub-tasks that I create under my stories. What change should I make to the branch rule? In other words, when a customer is updated at epic level, it should get updated on all stories below epic. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

1,758 views 2 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you