Usage-based billing starts December 3, 2026. To prepare, review your included allowance, current usage, and forecast in Atlassian Administration.View your usage
Automation FAQs
Automation
What is Automation, what counts as an "automation step," and how is it measured?
Automation is Atlassian's built-in workflow engine for repetitive tasks such as auto-assigning issues, sending notifications, and transitioning statuses based on conditions. You can build automations across Jira, Confluence, Jira Service Management, Jira Product Discovery, Customer Service Management, and Administration.
Automation usage is measured in steps. An Automation step is a single executed part of a flow:
Triggers: the event that starts the flow (e.g., "When an issue is created")
Conditions: narrows the scope of your flow (e.g., "If priority = High")
Actions: tasks the flow performs (e.g., "Send email", "Assign to user")
Branches: logic paths (e.g., if/else)
Loops: repeated iterations within a flow
Example: Trigger → check priority → assign user → send notification = 4 steps.
Your organization receives included Automation step allowances based on your subscriptions and plan tier, pooled at the org level. Allowances refresh monthly.
Important: Rovo-powered steps within a flow (e.g., "Use Agent," "Use Rovo") consume Rovo credits from your separate Rovo credits allowance, not Automation steps
What is changing with Automation usage tracking as of Dec 3, 2026?
Previously, Automation usage was measured in successful flow runs. Each completed flow counted as one run, regardless of how many actions it contained. Limits were set per-app and per-edition, and Enterprise customers had unlimited automation.
Here's what's changing:
New unit of measurement: Moving from measuring execution of entire flows to execution of individual steps within a flow, giving you granular visibility into exactly what's being automated.
Pooled allowances: Instead of per-app limits, your organization gets a single pooled allowance across all Atlassian apps, providing more flexibility in how you use automation.
Enterprise plans: Enterprise plans will no longer have unlimited automation. Instead, they receive pooled allowances designed to cover typical Enterprise usage patterns.
Pay-as-you-go option: If your organization needs more, additional steps cost $0.50 per 1,000 steps, or you can purchase Automation step packs (prepaid).
What stays the same:
Automation is still built into your existing subscription, no separate purchase required.
Your automation flows remain unchanged.
Allowances refresh monthly.
Which apps have Automation step allowances?
Each of the following apps/collections includes a monthly Automation steps allowance:
Jira
Confluence
Jira Product Discovery
Jira Service Management / Service Collection
Teamwork Collection
Your Automation steps allowance is pooled at the organization level across all apps, so steps consumed in any app draw from a single shared pool.
How are conditions counted?
Each condition counts as one Automation step when it runs, whether it passes or fails. How you set up your filtering can affect how many steps a flow uses:
Filters inside a trigger count as part of the trigger: If you add filter criteria directly to the trigger (e.g., "Work item updated where priority is High"), the trigger and condition count as one step.
A separate condition counts as its own step: If you use a general trigger followed by a condition (e.g., the trigger Work item updated, then the condition Priority is High), the flow uses two steps: one for the trigger and one for the condition.
One condition that checks several things still counts as one step: For example, a single condition that checks Priority is High and Status is Open counts as one step. If you split those checks into two separate conditions, they count as two steps.
What doesn’t count toward automation usage?
These runs and steps don't count toward your Automation steps allowance:
Runs that don't perform actions: Starting November 5, 2026, if a flow stops before it performs any action, none of the steps in that run count. These runs show "No actions performed" in your audit log.
Aborted or throttled runs: If a run is aborted or throttled, none of its steps count, including any steps that ran before it stopped.
Steps that fail because of an Atlassian error: If a step fails because of an error on Atlassian's side, it doesn't count.
System steps: Log action, Create variable, Create lookup table, Re-fetch work item data, and Lookup work items never count, even when they're part of a flow that does.
What counts as a run that doesn't perform actions? It's a run where a flow is triggered but stops at a condition before any action is performed. These runs show the status "No actions performed" in your audit log. For example, a flow triggers when a work item is updated, but stops because the work item doesn't match the condition.
Where can I monitor automation usage?
You can monitor usage across your organization or drill into app-specific automations:
Organization level (all apps): Organization and billing admins can see total aggregated step usage, overall trends, allowances, and billing cycle dates in Atlassian Administration → Usage → Meters overview.
App level (app-specific flows): The Automation → Usage tab within each app shows usage for flows running in that app. Admins can see a per-flow breakdown to pinpoint which specific automations are driving usage for that app and take action to optimize them.
How much does pay-as-you-go cost?
If your organization exceeds its monthly Automation steps allowance, additional steps are billed at $0.50 per 1,000 steps. You can estimate your pay-as-you-go cost with this formula: (Monthly steps consumed − included allowance) ÷ 1,000 × $0.50 = estimated pay-as-you-go usage charge
Example: (12,000 − 5,000) ÷ 1,000 × $0.50 = $3.50 estimated pay-as-you-go charge
Which specific automation features will be limited when my allowance is exhausted?
When your monthly pooled allowance is consumed, and your organization or billing admin has disabled pay-as-you-go:
New automation flows will stop: Triggering events won’t execute until your allowance refreshes at the start of your next monthly billing period, or until you add a usage pack/committed pack. Automation flows that are mid-flow (in-flight) will complete.
Events are not queued: Events that would have triggered a flow that occur while the flow is paused are not stored or replayed when the allowance refreshes.
Automation flows using manual triggers are also paused
What still works: Existing work items, workflows, and manual processes are unaffected, only automated flow execution pauses. Your flows remain configured and resume automatically once your allowance refreshes or a usage pack/committed pack is added. Admins can check the automation audit log to see which flows would have triggered during the pause.
How to avoid interruption:
Ensure pay-as-you-go remains enabled ($0.50 per 1,000 extra steps), so flows continue running.
Purchase Automation step packs (prepaid).
Monitor and optimize via the Platform usage dashboard.
Can I mark certain automation flows as "business critical" to protect them from degradation?
There is no way to designate individual flows for prioritized execution. However, you can protect important workflows by:
However, you can protect important workflows by:
Monitoring usage proactively: via the Platform usage dashboard in Atlassian Administration.
Proactive notifications: billing admins receive alerts at 80% and 100% of monthly usage thresholds.
Purchasing packs: Automation step packs (committed packs or usage packs) can be added at any time.
Optimizing lower-priority flows: simplify or reduce the frequency of non-essential flows to free capacity for critical workflows.
We're investing in giving admins more tools to manage and allocate capacity. We'll keep you updated on new capabilities on the roadmap.