Jira automation steps calculator
From December 2026, Jira Cloud automation is billed by the step. Drop the export of your rules below: see the steps each rule spends, your share of the allowance, the extra cost and what to change first. Free, nothing to install, and your file never leaves your browser.
How Atlassian counts steps
- A step is each trigger, condition, action, branch or loop turn that runs.
- A branch costs 1 step, plus its contents once for each work item it goes through. An if/else costs 1 step, plus the path that runs.
- A run where no action is performed uses no step (from 5 November 2026).
- Log, Create variable, Create lookup table, Re-fetch work item data and Lookup work items use no step themselves. Rovo and agent actions are billed as Rovo credits; third-party AI actions, such as Cursor or GitHub Copilot, count as steps.
Your allowance
Each product plan gives a monthly allowance, and the allowances of your organization are pooled: every site and app draws on the same total. Steps beyond it cost $0.50 per 1,000, or, with extra usage off, rules stop until the meter resets.
| Steps a month | Free (per site) | Standard | Premium | Enterprise |
|---|---|---|---|---|
| Jira | 150 | 400 per user | 750 per user | 1,000 per user |
| Jira Service Management | 1,250 | 3,000 per agent | 6,500 per agent | 9,500 per agent |
| Jira Product Discovery | 100 | 300 per user | 500 per user | 750 per user |
| Confluence | 50 | 100 per user | 250 per user | 500 per user |
What the calculator cannot know
How often your rules run, and how many work items a scheduled rule finds each time. Type the executions of each rule from Global automation › Usage. The free Automation Steps & Cost app does the same inside Jira and counts them for you, from your site’s real activity.
An estimate, not your bill: the reference is Atlassian’s meter, in Atlassian Administration › Usage. Source: Atlassian, How is my automation usage calculated. Your rules are read in your browser only: nothing is sent or kept.