Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,464,971
Community Members
 
Community Events
176
Community Groups

Can we set automation rule to wait to execute until previous execution is complete?

Colleen Gotling
Colleen Gotling Dec 07, 2022

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?

Answer
Watch
Like Be the first to like this
60 views

1 answer

0 votes
Ravi Sagar _Sparxsys_
Ravi Sagar _Sparxsys_ Community Leader Dec 07, 2022

Hi @Colleen Gotling 

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

Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events

See all events