Rare is the Jira Cloud Software customer with only a handful of automations. Most customers have hundreds of them to automate many processes across their Cloud deployments.
While the built-in Jira automation is a great place to start automating your workflows, it comes with execution limits. And with Atlassian’s changes to their automation packaging model (including stricter usage limits), it’s worth taking a closer look at how you’re using automations.
This is especially true if you’ve got a lot of rules to run, branches in your rules, or parallel rules that need to run. Keep reading to learn more about the new automation limits and how you can set them up so you avoid hitting the upper limits.
Automation limits for Jira Cloud
Before we dive in, let’s look at the changes in automation limits for Jira Cloud Software. Here’s how limits were previously counted and how they’re counted now.
Previous limits | Current limits |
| All Automation runs were combined into a single limit across all Jira Cloud licenses. | Each Jira Cloud product has its own limit and is measured per product license. |
| Any rule that was triggered counted towards the limit, regardless if it was successful. | Only rules that result in a successful action count toward the limit. |
|
|
Product and edition | Previous monthly | New monthly | |
Jira Software | Free | 100* | |
Standard | 500* | 1700 | |
Premium | 1000 per user*** | ||
Enterprise | Unlimited | ||
Jira Service Management | Free | 100* | 500 |
Standard | 500* | 5000 | |
Premium | 1000 per user*** | ||
Enterprise | Unlimited | ||
Jira Work Management | Free | 100* | |
Standard | 500* | 1000 | |
Premium | n/a | 100** per user | |
No Enterprise edition currently | |||
Jira Product Discovery | Free | n/a | 200 limits |
Standard | n/a | 500 limits | |
No Premium & Enterprise editions currently | |||
| * These limits were only for project and global rules. Single project rules were unlimited. ** Atlassian is monitoring usage and adjusting limits as needed. *** Atlassian aggregates Premium per user limits based on the total number of paid users. Source: https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update | |||
Here are some tips to overcome Jira Automation limits, maintain Jira performance, and continue to enjoy the benefits of automation for your business.
6 Tips to overcome automation limits
1. Optimize existing workflows
Review and optimize your existing automations. Identify rules that are redundant, are seldom triggered, or are associated with workflows that have changed. Make your rules detailed enough that actions are only triggered when specific criteria are met.
2. Prioritize critical automations
Identify and prioritize critical automations and allocate automation execution slots to your most important processes. For example, if you have rules triggering notifications, optimize the rule to only notify users on critical changes and not minor updates.
3. Consolidate rules
Over time, you might end up with multiple rules with similar conditions and actions that could be combined into a single rule. Combining and consolidating rules reduces the overall number of individual executions and saves slots for others. For example, if you have separate rules for transitioning issues to different statuses based on different conditions, consolidate these rules into a single rule that evaluates all the necessary conditions.
4. Adjust the rule frequency
Evaluate the frequency at which certain automations run. Change the schedule to run the rules less frequently if you don’t need real-time updates. For example, if you have a rule that updates data in real time, but the updates aren’t critical to your processes, adjust its schedule. Have it run once or twice a day during off-peak hours so you still get the information without impacting performance.
5. Monitor and adjust rules
Auditing rules regularly is essential to staying below the automation limits. Identify redundant or obsolete processes and the related automations. Check whether each automation can be deleted, or merged with another one. For example, you can turn off rules associated with temporary projects or workflows that no longer exist.
6. Consider third-party apps to avoid upgrading
Before upgrading to a higher Jira cloud tier, explore third-party add-ons such as JSU Automation Suite, Jira Misc Workflow Extensions (JMWE,) or Power Scripts which can be a more cost-effective option than upgrading to a higher Jira Cloud plan.
These apps provide unlimited executions, regardless of your Jira Cloud plan, so you can implement automations without monitoring the number of executions. Plus, you can go beyond what’s available in Jira’s built-in automation, including advanced automations like setting conditions, validators, or integrating with external tools.
Moving beyond automation limits
Automation limits help to maintain Jira Cloud’s performance at a high level. But they should work for you, not against you. Apply the tips in this article to optimize your workflows through consolidation, changes to run frequency, priority, and regular reviews.
If you’d like help analyzing your automation rules to make sure they’re well-designed and optimized for your Jira Cloud edition, contact Appfire today. Our automation experts can help you reach peak productivity.
