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

No Actions Performed, but automation is set up properly

When the status of an issue is changed, that is the trigger to update the corresponding field on the parent issue. Ex. the child ticket is being transitioned to "Review" status, and the parent ticket "Assessment" field needs to be updated to "Review"... why isn't isn't working!! Help!!Screen Shot 2021-02-22 at 4.11.47 PM.png

1 answer

1 accepted

0 votes
Answer accepted
Sherry Goyal
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 22, 2021

Hello @Julia 

I suppose, your branch condition is always returning false hence your rule exits before executing the action. You can check audit logs and verify this.

If you are working on issue types for which parent -> child relationship hold true, you can use "For parent" type directly, for example this.

Hope this helps!



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events