I wanted to discuss the recent change to Automation Billing for Atlassian's cloud products. This change is likely to affect many of you using
Atlassian’s cloud offerings and if not addressed can see your regular Atlassian bill increase by ~150%.
What is the change?
You may have noticed in a recent communication from Atlassian, in it, they state that they are adjusting their automation limits for Jira and Jira Service Management products, effective November 1, 2023. This means your team's automation usage will now be measured per action per product, and some limits will be reduced.
The new number of monthly executions per product are:
Jira Software: 1700
Jira Service Management: 5000
Jira Work Management: 1000
Jira Product Discovery: 500
If your instance clocks up more these new limits, then your automations will stop executing until the end of the month (count renewal) leaving issues unprocessed. I just want to point out how impactful that can be. No rules will process! P1 tickets may sit unattended, Tasks won’t get assigned, notifications may not be sent, reports will be incomplete… This will have a large and possibly irrevocable effect.
What constitutes an execution?
Thankfully Atlassian are also changing the criteria for what constitutes an execution of an Automation. Commencing on the same date as the limit is applied, Atlassian will now only record an execution of an Automation rule once an action has been applied. i.e.
A rule is triggered
A condition fails
Action not run
The above will not count towards an execution.
A rule is triggered
A condition passes
An action applied
The above will count towards the execution count.
This new assessment of what constitutes an execution will mean current execution levels, as shown in your “Global automation” Audit log should drop significantly. Will it be enough to meet the new thresholds? To cover you for the first 3 months of the change, Atla
ssian will provide a trial Premium license at the cost of a Standard license. However, using this trial to kick the can down the road, could ultimately prove costly.
What do we do?
Unfortunately there is no easy fix here, what is required is an audit of your existing rules to assess the impact of the change and then reviewing, rewriting and deleting your automation rules to strive for efficiency. Here are some steps to undertake:
Identify most triggered: Take a look through your audit log to find the most commonly run rules.
Evaluate Execution Frequency: Assess how often the actions are executed.
Refine conditions: Modify automation rules to target specific conditions.
Tiered conditions: Layer conditions and actions so only necessary actions are run.
Assess action necessity: Have you included nice to have actions that can be removed.
Test and document your changes.
Monitor your execution logs.
There are some other things that can be done to combine rules and to do more with single actions, but the steps above should provide you with good results without getting too complex.
Don't wait until the new automation limits take effect.
Take action soon and start to remedy the issues or reach out to us today, and let Simplicity optimise your Atlassian tools while staying cost-efficient. Together, we can ensure your teams continue to work seamlessly and productively without the need for costly premium licenses.
Comments