Guenov Labs
More free tools

Free tool

Jira automation usage calculator

Atlassian caps how many automation rule runs your site gets each month, and when you hit the cap every rule stops until the first of the next month. List your rules and how often they fire, and this works out whether you’re comfortably inside your plan’s allowance or heading for a wall. Everything runs in your browser — nothing is sent anywhere.

Your plan
Automation allowances are counted per product, per month.

Standard gives every site the same flat allowance, so user count doesn't change it. It's used if you switch to Premium.

Your rules
Add each automation rule (flow) and roughly how often it actually completes.
Automation rules

Start from an example

Typical rules with a rough default you can edit.

Estimated monthly usage
Standard · Jira

331

of 1,700 runs a month

080%1,700

You're at ~19% of your monthly allowance, with roughly 1,369 runs to spare.

Biggest consumers

  • Notify on issue done326
  • Scheduled weekly summary4
How this is estimated

Your estimate is simply each rule’s run frequency converted to a calendar month and added up. A month is treated as 30.44 days, 21.75 weekdays or 4.35 weeks — the yearly averages, since months vary and Atlassian’s counter resets on the 1st.

It compares that total to your plan’s published allowance. Free and Standard get a flat number of runs per product. Premium pools 1,000 runs per licensed user across the product, so the allowance is multiplied by your user count. Enterprise is unlimited.

Caveats worth knowing
  • Real usage varies. This is an estimate from numbers you typed, not a measurement — your actual figure lives on the automation Usage screen in Atlassian admin, and that’s the one that counts.
  • Only successful runs count. A rule that fires but fails its conditions performs no action and isn’t counted, so estimating from trigger frequency tends to overshoot.
  • Branches don’t multiply a run. A rule that branches over 50 work items still counts once — but it can hit separate per-execution service limits.
  • Chained rules do multiply. If one rule triggers another, each rule’s run is counted separately, so a chain of three is three runs.
  • Global and multi-project rules are billed to the product with the highest allowance, which may not be the product you expect.
  • On Free plans and trials, email actions have their own separate cap of 100 emails per 24 hours.

Monthly automation runs by plan

Each product has its own monthly pool. Limits reset on the first of each month at 00:00 UTC, and unused runs do not roll over.

Monthly automation rule runs included with each Atlassian Cloud plan
ProductFreeStandardPremiumEnterprise
Jira1001,7001,000 × usersUnlimited
Jira Service Management5005,0001,000 × usersUnlimited
Jira Product Discovery2005001,000 × usersNot available
Confluence101001,000 × usersUnlimited

Questions

What counts as an automation rule run in Jira?
A run is counted when a rule executes and successfully performs at least one action. A rule that triggers but fails its conditions — so it does nothing — is not counted. A single run counts once even if it performs many actions, and the log, create variable, create lookup table, re-fetch work item data and lookup work items actions don't count on their own.
Do single-project rules count towards the limit?
Yes. Since Atlassian's November 2023 packaging change, single-project, project-type, multi-project and global rules all count. Older guidance saying single-project rules are exempt is out of date.
How does the Premium allowance pool?
Premium grants 1,000 runs per licensed user per month, pooled across the whole product rather than capped per user or per rule. A 25-user Premium site gets 25,000 runs a month to share between every rule.
What happens when you hit the monthly automation limit?
Rules for that product stop running until usage resets on the first of the next month at 00:00 UTC. Unused runs don't roll over. Atlassian shows a warning banner in the automation screens when it predicts you'll pass the limit.
Are automation limits per site, per user, or per rule?
They're per product, per month, across the whole site. Every rule draws from the same pool. On Free and Standard that pool is a flat number; on Premium it scales with your licensed user count; Enterprise is unlimited.