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

How to Modify a parent issue with a value from a child issue


I have the following problem:


A parent is having several linked children (not subtasks). The parent and the children have a field "Due Date". The parent shall always carry the latest Due Date of all of the children. If a child gets a later Due Date, then it's easy to check if that child's due date is later than the parent's due date and the parent's due date can be updated accordingly. 

But if a child's due date is set earlier than the parent's due date, then I need an automation that checks all children's due date and sets the parent's due date to the latest one. 

I don't see that this is possible with automation for Jira since I cannot change a value of the triggerissue with the value of the linked issue.


2 answers

1 accepted

0 votes
Answer accepted

Hi @Cornelia Richter 

To clarify what you are trying to do, would you please explain:

  • When you indicate parents and children, not sub-tasks, do you mean Epics and Stories or Bugs?  Or some other way of organizing the issue relationships?
  • Why do you need to perform this additional check for earlier Due Date values?  If you check any created or edited issue for a Due Date later than the linked issue's (parent), wouldn't the later date would always "win".


Best regards,


1. these are linked issues.

2. I need to check any existing linked child issue (without editing) which one is the onr with the latest due date in order to copy that information to the linked parent

Like Keaghan Rilling likes this

Thanks for that information, @Cornelia Richter 

You are using links rather than the built-in parent/child relationships, so you can use JQL in a branch to find the related items.  You can then test if the "child" items have a later date and update the "parent".  With the server version, if you need any temporary storage during the rule execution, consider adding custom fields or properties to help.  (With cloud version, you could instead use Create Variable.)

For any linked children added before the rule was created, you could use a one-time rule with a scheduled trigger (or a manual trigger) to find and update the parent for those children as well.

One good way to get help on rules is to build the rule, note what is/is not working, and then post an image of the rule in your question.  That will help the community provide more targeted ideas for you.



thanks for answer, I have considered the mentioned solution already.

I will  post a snip of the automation next time

0 votes

Hi @Cornelia Richter are you on Server/DC or Cloud?

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,868 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