Problem Statement
I won't go over the enormous benefits of JIRA Automation, but it saved my teams and me from custom coding. However, if you use a standard plan for JIRA Cloud, the 500 executions/ month might become a challenge ( I've be honest, I've seen a few times: "You've reached your monthly rule execution limit. Upgrade your plan to increase your limit." and I didn't like it).
There are multiple solutions for optimizing the runs, but I've found the following rule the most beneficial:
Does the action need to happen instantly after the trigger is on?
If the answer is NO, use a CRON as a trigger.
You might say that this might not be acceptable for your situation, but definitely, there are scenarios where a few hours delay generated by the
Let's get to a practical example, starting with this JIRA automation idea :
When a ticket is transitioned in a certain status, I want to notify some in a Slack Channel
Solution 1 - w/o optimization
Pro: The action is run instantly ( I'm using the Slack API for sending the messages due to extended customization options)
Cons: The automation runs whenever a ticket is transitioned through the workflow
Solution 2 - optimized
Pro: The automation runs ~ 42 times/month
Cons: The Slack message isn't sent instantly
In this case, the CRON runs the following JQL query twice a day at 8:00 AM and 3:00 PM every working day.
status changed TO ("Final Acceptance") during (-1d, now()) and ( labels not in (SlackNotified)