Automation basics
Understand the general concepts and best practices of automation in Atlassian cloud products.
How is my usage calculated?
How is my automation usage calculated?
Automation usage is measured by the number of rules that run each month.
Usage limits vary by product and plan, but they always reset at the beginning of each month. Unused runs from the previous month will not roll over.
What counts as a rule run?
When an automation rule runs successfully, that is, it performs at least one action, it counts as a run. Each successful rule run counts only once toward usage, even if the rule performs multiple actions.
What doesn’t count as a rule run?
Rules that perform no actions
If a rule runs, but doesn’t successfully perform an action, then it won’t count towards your monthly usage. For example, let’s say we had the following rule set up in Confluence:
Trigger: When a page is published
Condition: If {{page.title}} contains Retro
Action: Then add a label, Sprint retro notes
The rule will trigger every time a page is published - however, the run will only count towards your usage if the page title contained Retro and the label Sprint retro notes was added successfully.
Actions that don’t count
The following actions don’t count toward your automation usage:
Log action
Create variable
Create lookup table
Re-fetch issue data
Lookup issues
If your rule runs, but it only performs the above actions, that run won’t count towards your usage.
System rules
In Jira Cloud, some project templates come with automation rules already set up - these are called system rules. When system rules run, they don’t count towards your usage.
Currently, there are no system rules in Confluence.
What are my usage limits?
Usage limits 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.
Number of rule runs per month | ||||
|---|---|---|---|---|
Free | Standard | Premium | Enterprise | |
Jira Work Management | 100 | 1,000 | 1,000 multiplied by the number of users | Plan not available for Jira Work Management |
Jira | 100 | 1,700 | 1,000 multiplied by the number of users | Unlimited |
Jira Service Management | 500 | 5,000 | 1,000 multiplied by the number of users | Unlimited |
Jira Product Discovery (Currently in Early Access mode) | 200 | 500 | 1,000 multiplied by the number of users | Plan not available for Jira Product Discovery |
Confluence | Automation not available in Free | Automation not available in Standard | 1,000 multiplied by the number of users | Unlimited |
How rules are billed to each Jira Cloud product
Each automation rule is assigned to a product, and will count towards that product’s monthly limit. This is based on the following criteria:
Rules scoped to a specific project will be billed to that project’s product.
Rules scoped to a project type will be billed to that product
E.g. if a rule is set to run for all software projects, it will be assigned to Jira.
Rules scoped to multiple projects will be assigned to the product that has the highest monthly limit
E.g. Let’s say you’ve signed up to Premium plans for Jira and Jira Service Management.. And let’s say you create a rule that runs across all three
Global rules will be billed to the product with the highest automation limit.
If you have Jira Work Management included in your license
Jira Work Management comes free with Jira Software and Jira Service Management. If you’ve purchased a Jira Software or Jira Service Management license, you won’t see Jira Work Management in your Usage. In this case, rules that would usually be billed to Jira Work Management will instead be billed to the product with the highest limit.
How is usage tracked?
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.
What happens if I reach my monthly limit?
If our system predicts that your team will pass your monthly execution limit, you’ll see a warning banner whenever you go to Automation. For example, this might happen if you reach 50% of your monthly in the first week.
If your team reaches the limit of allotted executions, your rules will fail to run until usage resets on the first of the following month.
The exception to this is system rules - these rules will always run, unless you disable them. Learn more about system rules
When will my monthly limit reset?
Automation usage resets for all products on the first of each month at 00:00 UTC (coordinated universation time).
How does usage work for annual subscriptions?
If your plan is billed annually, you’ll remain on the previous Automation packaging model (i.e. have unmetered rule runs for single-project rules) until your current plan is up for renewal and you sign a new contract. From then on, you’ll be subject to the current packaging model, and your automation usage will reset every month.
However, please note that user tier upgrades will count as a new plan - so if you upgrade your user tier, your site will start using the limits listed under What are my usage limits?.
Was this helpful?
Still need help?
The Atlassian Community is here for you.