10/15/2026
Your automation rules are about to be measured differently.
From December 3, 2026, automation across Jira, Confluence, Jira Service Management and Jira Product Discovery is billed on a new meter: automation steps, pooled across your organization.
Instead of looking only at how many times a rule runs, Atlassian counts the ex*****on steps inside each run, including:
• Triggers
• Conditions
• Actions
• Branches
• Loops (for each)
That means two rules that each run 100 times a month can draw very different amounts from your allowance, depending on how they're built.
One more thing to know: agent components in a rule, such as Use Rovo, Use agent or Use Jira Coding Agent, draw on your Rovo credits, not automation steps. One rule can touch two meters at once.
Most teams built their automations to work, not to be efficient. Until now, nobody needed to know how many steps a rule used.
Our new blog explains how the automation steps meter works and what it means for the rules you already have: https://hubs.ly/Q04B6GXR0