How is my usage calculated?

Automation usage is measured by the number of rules that execute each month. However, what counts as an execution — and which executions count toward usage — can vary between products.

Usage limits can also vary by product, as well as by plan, but they always reset at the beginning of each month. Unused executions from the previous month will not roll over.

What counts as a rule execution?

Jira

Any time an event in Jira Software or Jira Service Management fires as a result of an automation rule you have enabled, it will count as a rule execution.

For example, if you have created a rule that fires whenever an issue transitions to Done, this will count as a rule execution. Even if the rule does not perform an action, as long as it has been triggered, it is considered an execution.

Confluence

When a Confluence automation rule runs successfully, that is, it performs at least one action, it counts as an execution.

 

What counts toward usage?

Jira

Single-project, multi-project, and global rule executions

All multi-project and global rule executions will count toward your usage. Single-project rule executions do not count toward your usage.

A single-project rule is a rule that automates a task or process that only affects one project. Multi-project rules are rules that automate tasks or processes that affect more than one project, while global rules automate across all projects in your instance.

One exception to this is the cross-product Issue create action. For example, if you want to create an issue in Jira Software based off an event in Jira Service Management — this will count as a single-project rule, not a global rule.

Confluence

Space and global rule executions

All space and global rule executions count toward usage. However each successful rule execution counts only once toward usage, even if the rule performs multiple actions.

If a rule is triggered but fails without performing an action, it does not count as an execution and therefore doesn’t count toward your monthly usage limit (if your plan has one).

 

What are my usage limits?

Usage limits also vary by product and plan, but they always reset at the beginning of each month. Unused executions from the previous month will not roll over.

Jira

All plans have an unlimited number of single project rule executions, as they don’t count toward usage.

Jira Enterprise also has an unlimited number of multi-project and global project rule executions.

Jira Premium is limited each month to a pooled sum that’s equivalent to 1,000 multi-project or global project rule executions for every user.

For example, 200 users will have 200,000 global/multi-project rule executions each month.

Jira Standard has 500 multi-project or global project rule executions to trial each month.

Jira Free has 100 multi-project or global project rule executions to trial each month.

Confluence

Confluence Enterprise has an unlimited number of rule executions.

Confluence Premium is limited each month to a pooled sum that’s equivalent to 1,000 rule executions for every user.

For example 200 users will have 200,000 rule executions each month.

Automation is a premium Confluence feature for admins and isn’t available in Free or Standard at this time.

 

How is usage tracked?

Jira

On the Usage screen, you’ll find an outline of your monthly automation usage, and how you’re tracking against your plan’s limit.

Learn more about how to access and understand the Usage screen.

Confluence

Confluence admins can track usage in the automation Usage screen. Site admins can see a running total of the number of rule executions used across all spaces each month. Product and space admins can monitor the number of executions used by individual rules.

 

What happens if I reach my monthly limit?

In any Atlassian product with automation…

If your team surpasses 90% of your plan’s usage limit, a warning banner will appear at the top of the usage screen.

If your team reaches the limit of allotted executions, your rules will fail to run until usage renews on the first of the following month.

Additional Help