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

Automation: child to inherit parent fields


I want the sub-task to inherit two fields (components and a custom field which is called Menu Analytics OKR) from the parent task.

I have tried two variation to try to get it to work, but neither seem to work.


Screenshot 2021-08-16 at 17.07.10.png


Screenshot 2021-08-16 at 17.08.34.png

I also want the child sub task to update if the parent changes. This doesn't work either.


Screenshot 2021-08-16 at 17.06.54.png

Any help would be much appreciated. :)

1 answer

0 votes

Hi @Zara Hughes 

Did you check the audit log of the automation you tried?

Did the automation rule get trigger?

Did it trigger for the right issue?

I would suggest you to add "log" action, to print to the audit log, what parent issue running the rule, what child issue running, what is the value of parent components you try to copy (to check it gets the values right).

Then update us the outcome and we will look further :)

Thanks for your help :)

I created a new sub - here is the log.

It seems to recognise the sub task, but doesn't appear to find the parent.


Screenshot 2021-08-16 at 18.28.31.png

Nir Haimov Community Leader Aug 16, 2021

No problem :)

OK  this is good progress, now print to the logs the parent issue key, so we will see if it recognize the parent.

Also, print to the logs the fields values from the parent (and check manually that the parent actually have values on these fields)

Thanks for your help with this, I managed to get it sorted.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events