The five meters affected
1. Rovo credits
AI actions draw from an included credit allowance; usage beyond that is billable.
Uses credits: Rovo Chat, Agents, Think Deeper, Coding Agent, third-party API calls
Always free: search, summaries, inline suggestions
2. Automation steps
Moves from counting flow runs to counting steps; for example, a 2-step flow and a 20-step flow each used to count as one run. Now every action, condition, branch, or loop counts as one step.
Enterprise plans no longer include unlimited automation; instead, they offer a monthly allowance.
3. Assets objects
- Assets: new capability for Jira and Teamwork Collection customers
- Service Collection: no change to allowance or pricing, but gain centralised visibility in Admin Hub
- Unique asset records stored at any point in the billing month are counted
4. CSM AI resolutions
Atlassian's first outcome-based meter: you only pay when AI fully resolves a ticket end-to-end with no human involvement. If there is no resolution, then you are not charged.
5. Bitbucket (build minutes, Git LFS storage, packages storage)
Now centrally managed in Atlassian Administration.
Monthly plans: allowances move from workspace-level to org-level, giving more flexibility under the same billing model
Annual plans: usage beyond the included allowance is billable
Failed builds still consume build minutes, but self-hosted runners do not count towards the meter.