You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have an automation rule that triggers when a new issue is opened. It does a lot of stuff to the Epic like calculating total story points, number of issues, percent complete, etc. Therefore, this takes about 40 seconds to run. The problem is that there are times child issues are opened quickly and the rule triggers a second time but the first rule is still running. I believe this is causing issues with the calculations. Is there any sort of "wait for previous execution to complete" setting?
You can split your rule into two rules where the second rule will be triggered after 1st rule is finished. There is an option in the automation for a rule to be triggered by another rule.
May be in your 1st rule you can update a field just to ensure that your second rule is not executed without that field getting updated value.
Ravi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.