Automation Rules execution limits on Jira Standard

Pedro Celdrán
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 28, 2024

My company currenly is using Jira Cloud Premium. They are going to downgrade to Standard.

We have around 30-40 users in total.

We have currently running several automation rules. I have read that the number of runs of this rules is limited to 1700/monthly on Jira Standard. 

How can I know how many rules are being currently executed monthly in our Jira? My concern is whether we will be out of limit when we go to Standard from Premium or not.

2 answers

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 28, 2024

Hi @Pedro Celdrán -- Welcome to the Atlassian Community!

Adding to the other suggestions...

The automation usage limits by products, license types, and number of customers may be found here: https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/#What-are-my-usage-limits

 

That is only one of the things to check when planning to change license level...

Moving from Premium to Standard level will also reduce the "Number of rules that can run at the same time" from 20 to 10 rules at once: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/#:~:text=Number%20of%20rules%20that%20can%20run%20at%20the%20same%20time

This means half as many rules run at once, potentially leading to other challenges as rules are delayed, waiting for their "turn" to run.

I recommend reviewing your global automation audit log for the last 60 days, looking for any patterns of heavy usage at once, or even the condition of "throttling": https://support.atlassian.com/cloud-automation/docs/automation-service-limits/#Breaching-limits  These will indicate potential changes in rule usage and effectiveness.

 

A preventative measure to help is to add a global execution rule with the Service Limit Breached trigger: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Service-limit-breached

This could alert you sooner that problems may happen.  For example:

  • trigger: Service Limit Breached
    • When to trigger: pick a threshold you want, such as 80% of service limits
    • Maximum number of times this rule triggers: once per day, once per 12 hours, or once per hour
  • action: notify the Site Admins, such as with an email or Slack message

 

Kind regards,
Bill

0 votes
Tomislav Tobijas _Koios_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 28, 2024

Hi @Pedro Celdrán ,

If you're a Jira admin, you can navigate to System > Global automation and select tab Usage to check usage trends over the last period.

2024-11-28_10-18-09.png

Here's the official documentation on viewing usage: View your automation usage 

Hope this helps.

Cheers,
Tom

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events