Monthly Automation Limits on Cloud Jira

Atlassian announced recently that they are launching new automation limits for all cloud Jira products on Nov 1, 2023. This will include:

• Jira Software

• Jira Service Management

• Jira Work Management

• Jira Product Discovery

Per the announcement, each product edition (Free, Standard, Premium, etc.) will now have a fixed number of monthly automation rule limits. Atlassian’s goal is to make the automation experience consistent and scalable as they expand automation across Atlassian products.

Key Takeaways

With this change, there are a few important things to be aware of:

1. No more unlimited automation rules on any version.

2. Pooling of automation limits across Jira products will be removed.

3. Only successfully run rules will be counted vs counting all rules.

4. The following products will have the number of limits changed:

   1. Jira Software (Standard) | Currently: 500, New: 1700

   2. Jira Service Management (Free) | Currently: 100, New: 500

   3. Jira Service Management (Standard) | Currently: 500, New: 5000

   4. Jira Work Management (Standard) | Currently: 500, New: 1000

   5. Jira Work Management (Premium) | Currently: NA, New: 100 per user

   6. Jira Product Discovery (Free) | Currently: NA, New: 200

   7. Jira Product Discovery (Standard) | Currently: NA, New: 500 per user

5. If a product reaches its monthly run limit, then automation rules mapped to that product will stop executing.

6. If more automations are required than are available, users can upgrade to the next product edition. (e.g. Free to Standard, Standard to Premium, etc)

7. Global Administrators will be able to see the automation usage in the new Enhanced Automation Usage tab in Jira.

What can I do in advance?

1. Be proactive. Your Global Administrator should set regular tasks to review usage and optimize and upgrade as necessary.

2. Check if you are able to combine two or more rules using Conditions to create one rule.

3. Consider if you can use global or multi-project rules in place of several single-project rules. (Note: Using single-project rules improves efficiency compared to multi-project or global rules.)

4. Check the usage of certain rules and determine if any of them need to be disabled to prevent exceeding the usage limit.

We know this is a big change. If you like guidance on optimizing automations, developing a product strategy, or gaining an understanding of alternative solutions, E7 is here to help.