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
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
Hello Community 👋
We are expanding the same packaging model that was released with Confluence Automation earlier this year to our Jira Cloud family of products. These changes will come into effect on November 1, 2023.
Today, Automation usage is measured differently across both rule types and Atlassian products. Currently, there is only one limit for all Jira Cloud products. Every time an Automation rule runs, it counts towards that limit regardless of whether it performed a successful action or not. The new packaging model brings a simpler, more consistent way to measure automation usage. Each product will now have a fixed number of monthly rule runs based on the plan.
Here is a summary of the key changes for Jira Cloud products:
In today’s model, rule runs count toward your usage limit, even if they perform no actions. For example, let’s say you have the following rule set up:
This rule would trigger and count toward your execution limit every time an issue was created, even for issues that aren’t bugs. In the new model, the rule will only count if the issue created is a Bug and the Affects version field is successfully updated.
In today’s model, customers get a single, pooled limit across all Jira products. For example, if a customer has JSW Standard and JSM Free, they would get a total of 600 automation rule runs per month (100 from JSW Free and 500 from JSM Standard) that can be used across both products.
Each Jira product will have its own usage limit in the new model. Every automation rule draws on the limit of a specific Jira product when it runs. We have even increased the limits for our Free and Standard plans. Automation limits in the new model are shown below:
3. How will rules be counted in the new model
In today’s model, an automation rule that is configured to run in a single Jira project does not count toward the usage limit. In the new model, all automation rule types (i.e. single project, project type, multi-project, and global rules) will count towards the usage limit.
As we expand automation to Atlassian products beyond Jira, these changes enable a simpler and more consistent usage attribution model for automation - allowing customers to use automation more efficiently for cross-product and cross-team collaboration.
We’ve also taken this opportunity to increase usage limits to give customers a larger runway to manage this change and confidently grow automation usage in the future.
Here are a few suggestions to help you prepare for the change coming into effect on November 1, 2023.
From October 1st -31st, 2023, you’ll see a Preview option on the Global Automation screen next to the current Usage tab.
This will help you understand how your usage translates into the new model. We will not be enforcing new model limits during this period.
If the new usage tab (available October 1st) shows that your automation usage is breaching (going over) the new limits, we recommend looking at your current rules and optimizing them to lower your usage. Here are some things you can do:
Please reach out to Atlassian Support or your Atlassian Solution Partner to get help with understanding and managing your automation usage.
We’ve done a comprehensive assessment of automation usage across all customers to understand the potential impact of this change. Customers who may breach limits when the new model goes into effect on November 1, 2023 will receive a 3-month Premium trial offer with access to higher Premium automation limits and features. The trial will give customers more time and headroom to assess their automation usage. Customers can also review usage during the preview period mentioned above to check for potential breaches.
If you’re on an annual Atlassian Cloud subscription and approve a valid annual quote dated prior to October 18th, 2023 – limits in the new model will apply on the next renewal date. Please reach out to your Customer Advocate to learn more about the impact this will have on your subscription.
The following actions won't count towards your usage:
If a rule runs and it only performs the above actions, then the rule won’t count toward your usage.
From November 1, all automation rules (both new rules, and rules that you’ve already created) will automatically be assigned to a product. Here’s how this will work:
Single-project and project type rules: These rules will be assigned to the product of that project or project type.
For example, a rule that runs for all Service management projects will be assigned to Jira Service Management. Each time that rule runs, it will add to the monthly usage for Jira Service Management.
Multi-project and Global rules: These rules will be assigned to the product with the highest monthly limit.
For example, let’s say you’ve signed up for Jira Product Discovery Standard (500 runs per month), Jira Software Free (100 runs per month), and Jira Service Management Premium (1000 runs, multiplied by the number of users).
If you create an automation rule that runs across a Discovery project and a Software project, the rule will be counted as a Jira Product Discovery rule, because this is the product with the higher limit.
Confluence Cloud is already on the new model. We are making these changes to Jira Cloud Automation to make the experience consistent across our products.
These changes are only for Jira Cloud. The Automation for Jira app will remain unchanged for Jira Server and Jira Data Center.
If you have any other questions not covered here, please Contact us.