Jira automation is a no-code rule builder that lets users build "if-this-then-that" rules to automate their processes. The rules are triggered by Jira events and are relatively simple to build. Anyone with Global or Project Admin permissions can create automation rules to quickly automate many processes.
Automation is included with every Jira Cloud Standard, Premium, and Enterprise offering. However, there are notable Global and multi-project rule limits that may impact your experience with Jira's automation offering.
Jira Cloud StandardA total of 500 global and multi-project rule executions per month.
Jira Cloud Premium
1000 Global and multi-project rule executions per paid user per month, collectively pooled across all Jira tools and all users.
I.e., an instance with 200 users will have 200,000 monthly global/multi-project rule executions.
Jira Cloud Enterprise
Unlimited number of Global and multi-project rule executions.
With each Jira plan, you get a certain amount of rule executions per month. You may ask - how is "rule execution" defined? Every time a rule runs - an action is triggered - it counts as an execution.
As you can see above, in multi-project and Global automations, Jira Cloud Standard allows for a maximum of only 500 executions per month. This is a very small amount and can often be reached in hours or even minutes. If your team exceeds this limit, automations stop running.I want to point out that Atlassian has set expectations on this offering just right - it does not promote multi-project and Global rules features on their feature & pricing page for Jira Cloud Standard. However, with Jira Cloud Premium, you can execute much more Global and multi-project level rules to scale more easily.
Here are options to consider:
Option 1: Sign up or upgrade to Jira Cloud Premium or Enterprise.
Option 2: In Jira Cloud Standard, use Jira Misc Workflow Extensions (JMWE) to set up an unlimited number of automations - per project, multi-project, and global. JMWE offers you many ways to automate your Jira processes: through workflow automations, and through automations outside of workflows powered by our Event-based Actions. You can even reuse configurations with JMWE's Shared Actions to make this process even easier to deploy and maintain.
Also, check out this JMWE's Buyer's Guide (also available in PDF). While it covers many of JMWE's advantages, it will also help you understand how it compares to native Jira automation features, and other types of automation apps.