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.
Can Automation for Jira cause infinite loops?
The simplest case is a rule that triggers itself like the example below but one could conceive more complex setups involving Workflow postfunctions or Scriptrunner listeners.
How does jira handle these kind of situations?
br
/David
Actually, Jira Automation includes protection against such infinite loops, and will "break the loop" after 10 or 20 iterations (I don't remember the number exactly).
But yes, you'll end up with 10 or 20 extraneous comments :)
Tested my silly Comment-automation (in a test env.)
only one comment added, Automation ran 10 times according to the logs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
Yes, an infinite loop like that can happen. You need to add some type of condition to identify who is adding the Comment or set some type of custom field when you add the comment - but you will still need to be able to differentiate who/how the comment is added.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.