Jira Automation Is Metered From December 3, 2026
Every trigger, condition, action, branch and loop your automation rules execute becomes a billable step — even the runs that match nothing. Here's exactly what Atlassian's own documentation says counts, and what to audit before the meter turns on.
What Counts as a Step
Atlassian's own automation usage documentation defines it plainly: “An automation step is a single executed part of an automation flow, including triggers, conditions, actions, branches, and loops.” Each one below counts as one step when it executes:
Trigger
The event that starts a rule — counts as a step every time it fires
Condition
Every condition checked, whether it passes or fails
Action
Every action executed — comment, transition, field update, webhook, etc.
Branch
Each branch a rule executes, including branches over linked or related items
Loop
Each iteration of a loop — a loop over 500 items is up to 500 steps, not one
It Bills Whether the Rule Does Anything or Not
Atlassian's documentation lists the run outcomes that consume allowance — and it's all of them. A scheduled rule that fires every night and matches nothing still burns steps, every night, forever:
| Run outcome | Billed? |
|---|---|
| SUCCESS | Yes |
| NO_ACTIONS_PERFORMED | Yes |
| SOME_ERRORS | Yes |
| ABORTED | Yes |
| NO_MATCH — the rule ran and matched nothing | Yes |
What Rules Actually Cost: Measured, Not Estimated
Mihai Perdum of LeanZero built 11 rules on a test site on 15 October 2026 and reconciled Jira's Usage tab against the audit log. It is the only reproducible per-rule step data we have found. It is one author's measurement, not an Atlassian figure.
| Rule behaviour | Steps billed |
|---|---|
| Trigger fires, JQL condition says no | 2 per run |
| Same rule, condition matches | 3 per run |
| Scheduled rule that finds nothing | 1 per run |
| Branch over 5 sub-tasks, one comment each | 7 |
| If/else rule, by the arm that runs | 4, 5 or 6 |
| Transition that fails | 3 per run |
Two forgotten copies of one test rule accounted for 88% of the site's 4,091 steps for the month. And a five-minute scheduled rule that never matches anything runs 8,640 times a month and costs $4.32 a month at the overage rate (before any allowance is applied). The author did not test loops, lookups, smart-value conditions or Jira Service Management rules.
Runs that match nothing are still billed. Atlassian's automation usage documentation lists NO_MATCH among the run outcomes that consume steps, and LeanZero's measurements show what that means in practice: a trigger whose JQL condition fails still bills 2 steps, and a scheduled rule that finds nothing still bills 1 step on every run. Older Atlassian pages that describe no-match runs as free are out of date.
Extra Usage Is On by Default
Atlassian's usage-based pricing page states that extra usage is “enabled by default and billed in arrears,” with alerts at 80% and 100% of allowance, and that when a limit is reached “only the specific meter that has been exhausted” pauses. That inverts the protection most admins expect: the customer who does nothing gets a variable invoice, and the customer who deliberately opts out of overage billing is the one who gets automation that stops running mid-month. Deciding which side of that you want to be on is worth doing before December 3, not after the first metered invoice.
Atlassian's own automation usage documentation now states it directly: “Extra usage is billed at $0.50 per 1,000 additional steps.” That closes the gap left when this figure was reported only by TechRepublic on 3 September 2026 — it's Atlassian's number now, not a secondary source's.
Two Doors, and Neither One Is “Under Control”
Turn extra usage off to cap the bill, and Atlassian's own automation documentation is direct about what happens next: hitting 100% of allowance stops every flow in the meter, and it stays stopped until your usage resets — on your subscription's billing date, not the first of the calendar month.
“Hitting 100 percent stops every flow until your usage billing date, which is your subscription's date, not the first of the month; a 20 November overrun with a 3 December reset is thirteen days without automation.”
Sami Shaik, an Atlassian Community Rising Star, laid out the mechanism on 8 September 2026: the outage length isn't a fixed grace period, it's whatever's left between the day you cross your allowance and the day your subscription's own billing cycle resets it. Leave extra usage on and the bill is uncapped. Turn it off and automation can stop mid-project for up to two weeks, on a clock tied to your renewal date rather than the calendar. An admin can walk through one door or the other — there isn't a third door where usage-based automation stays both bounded and always-on.
What Your Automation Actually Costs
Monthly rule executions × average steps per execution, against your org's pooled allowance. The default below is one five-minute scheduled rule that never matches anything: LeanZero measured a scheduled rule that finds nothing at 1 step per run, so it executes 8,640 steps a month and bills all of them. The inputs are yours to change; the defaults are this site's illustration, not Atlassian figures.
Step count per run: LeanZero, 15 October 2026 (a measurement on a test site, not an Atlassian figure). Allowances and the $1 per 1,000 additional steps overage rate are Atlassian's, billed in arrears from December 3, 2026. This estimates one plan's pooled allowance against total org executions across all rules, not a single rule in isolation.
The Published Monthly Allowances
Per-user-per-month, and pooled across your whole organization — Atlassian's billing documentation states the org-wide allowance for a meter is the sum of every subscription's allowance for that meter. Unused allowance does not roll over to the next month.
| Plan | Automation steps allowance |
|---|---|
| Jira Free | 150 per subscription |
| Jira Standard | 400 per user |
| Jira Premium | 750 per user |
| Jira Enterprise | 1,000 per user |
| Confluence Free | 50 per subscription |
| Confluence Standard | 100 per user |
| Confluence Premium | 250 per user |
| Confluence Enterprise | 500 per user |
Automation steps are one of seven meters Atlassian has now published allowances for — the others are Rovo credits, Assets objects, four separate Bitbucket meters, and AI agent resolution for Customer Service Management. Atlassian publishes a unit price for Rovo credits ($10 per 1,000) but not yet for the rest. See how your own headcount and plan size against these allowances →
What to Audit Before December 3
Scheduled rules that sweep large JQL results
A rule that runs against a 300-item filter today and a 4,000-item filter next year gets more expensive with no change to the rule itself — the automation didn't change, the data it touches did.
Branches over linked or related work items
Branching logic multiplies steps in proportion to how many items it touches. A branch over a story's ten linked tasks is roughly ten times the steps of the same rule with no branch.
Rules nobody has opened in years
A scheduled rule left running since 2022 that matches nothing every night has been silently free. On December 3 it starts consuming — and eventually costing — allowance for doing precisely nothing.
Your extra-usage setting
Decide deliberately whether you want automation to keep running past your allowance (variable invoice) or pause (automation stops mid-month) — the default is billing, not pausing.
Automation You Host and Meter Yourself
See what your actual footprint costs against a platform where automation isn't a metered add-on.
Size My InstanceRelated Reading
Sources
- Expanded usage-based pricing — Atlassian company news (Tamar Yehoshua, 1 September 2026)
- How is my usage calculated? — Atlassian automation documentation
- Usage-based pricing — Atlassian
- Usage charges and billing — Atlassian Support
- Rovo usage limits — Atlassian Support
- "Automation steps start billing on 3 December" — Sami Shaik, Atlassian Community (8 September 2026, edited 10 September)
- Jira Automation Usage: Steps per Rule, Measured — Mihai Perdum, LeanZero (15 October 2026)
Last verified: 18 October 2026. Drawn from Atlassian's own announcement and support documentation. The $0.50-per-1,000-steps overage rate was confirmed directly on Atlassian's automation usage documentation on 9 September 2026, and the calculator's default scenario uses LeanZero's 15 October 2026 step measurements — re-verify all figures directly at support.atlassian.com before making decisions based on this page, and again after December 3, 2026.