Usage-Based Billing: Jira Components Starting in December 2026

Platform Usage and Quotas

Starting December 3, 2026, Atlassian will introduce usage-based billing for certain components. Platform usage tracks and reports how quotas—such as Rovo credits, automation steps, or Assets objects—are used within an organization.

Organization administrators can monitor usage, set usage limits, and adjust settings as needed. Quotas are generally pooled at the organization level. This allows users or locations to share a common quota, rather than having usage tracked separately for each app.

If the usage limit is reached and the option for additional usage has been enabled,

• organization and billing administrators receive notifications at 80% and 100% of the usage limit;
• the affected features continue to run without interruption;
• and the additional usage is billed at the end of the billing period on the next invoice.

Administrators can disable the additional usage or set appropriate spending and usage limits.

The Billing Models for These Components Will Change

Usage is tracked differently depending on the function. For example, Rovo Credits are required for certain AI interactions, while for automations, individual steps executed (previously, automation runs were counted) are deducted from the quota. AI agents are billed as a resolution only if they resolve a customer inquiry completely and without transferring it to a human team.

Rovo Credits

Rovo Credits are used for certain AI features and for accessing enriched context from the Teamwork Graph. Which actions consume credits depends on the specific feature and, in some cases, on the complexity of the request.

Included Rovo Credits

Shared Use at the Organizational Level

An organization’s total Rovo balance is combined into a shared pool. This allows users with higher needs to use more credits, while users with lower needs spend fewer.

Credits are also aggregated across eligible apps and collections. For example, a customer with Jira and Confluence licenses receives the combined Rovo credits from both apps—depending on the edition purchased for each.

A future update will make it possible to assign Rovo credits to individual users on a targeted basis.

Sample Calculation

An organization has 100 Confluence Premium users and 100 Jira Premium users.

The monthly calculation is as follows:

100 x 70 credits for Confluence
+ 100 x 70 credits for Jira
= 14,000 Rovo credits per month

The included credit allowances are updated monthly on the respective billing date. Unused credits are not carried over to the following month.

Automation Steps

In the future, Atlassian Automation usage will be measured in individual steps. An automation step is an executed part of an automation workflow. This includes triggers, conditions, actions, branches, and loops.

Each organization receives a quota of automation steps, depending on its subscriptions and plans. This quota is aggregated at the organizational level.

Example of the Shared Quota

The example organization has the following licenses:

• 100 Jira Premium users: 100 × 750 = 75,000 automation steps.
• 100 Confluence Standard users: 100 × 100 = 10,000 automation steps.

The combined monthly quota is therefore 85,000 automation steps.

Quotas are updated monthly. Unused steps do not carry over. Additional automation steps are billed at the applicable Atlassian rate.

What Counts as an Automation Step?

An automation step is defined as a function executed within a workflow. This includes:

• Trigger: The event that starts a workflow.
• Conditions: The logic that determines whether the workflow continues.
• Actions: The task that the workflow performs.
• Branches: Alternative paths, such as those using `if` and `else`.
• Loops: Repeated actions within a workflow, such as `for each`.

A step is considered completed when its execution results in one of the following statuses:

• SUCCESS: The step was completed successfully.
• NO_ACTIONS_PERFORMED: The step was executed but did not result in any changes.
• SOME_ERRORS: Business errors occurred during execution, for example, due to an incorrect configuration.
• ABORTED: The step was aborted before completion.
• NO_MATCH: Even if a trigger finds no match, the trigger’s execution is counted as a step.

Automation steps that call AI functions—such as “Use Rovo,” “Use agent,” or the Jira Coding Agent—are billed separately using Rovo credits and are not counted as additional automation steps.

Assets Objects

Each location has a fixed quota of asset objects. The number depends on the specific plan and edition.

The location quotas are combined into a single, organization-wide total quota. Usage is therefore tracked collectively across all locations within an organization and not separately for each location.

Regardless of the available total quota, each location can contain a maximum of 3 million objects. This limit applies even if unused quota is still available at other locations.

What Are Rovo Credits Used For?

Rovo Credits are consumed by billable events. Which actions are considered billable depends on the function being used.

Examples:

• In Rovo Chat, every user message can constitute a billable event.
• For Atlassian agents and other AI features, each invocation may count as a billable event.
• The number of credits used may depend on the complexity of the request and the computational effort required.

Not every AI feature is automatically billed in the same way. Therefore, it is recommended to regularly monitor usage via “Atlassian Administration.”

Solutions Provided by AI Agents

Usage fees for solutions provided by AI agents will take effect on December 3, 2026. Until that date, no fees will be charged for this usage.

AI agents are available in the Standard, Premium, and Enterprise plans. They are not available in the free plan.

A resolution by an AI agent is billed only if the agent fully resolves a customer inquiry without escalating the conversation to the appropriate team. The agent must provide a complete response, and the system must mark the conversation as resolved.

There are two billing options available, which can also be combined:

• Usage-based billing: currently $1 net per resolution
• Solution packages purchased in advance

Solution Packages

With an annual contract, companies can purchase solution packages in advance. Discounts are available for larger purchase volumes.

The solutions included in the package are distributed evenly over twelve months and credited to the quota on a monthly basis. Unused solutions expire at the end of the respective monthly billing period and are not carried over to the following month.

Bitbucket Metrics

On Bitbucket, the included quota depends on the plan you choose. Relevant factors include build minutes, Git LFS storage, package storage, and network transfer.

The Premium plan includes, among other things:

• Merge Checks
• Deployment Permissions
• IP allowlisting
• Two-factor authentication
• Access Controls
• Shared Pipeline Configurations

Additional Quota Extensions

Actual billing may vary depending on the specific contract, pricing plan, and billing cycle. Companies should therefore review the current Bitbucket pricing and terms of service before starting usage-based billing.

Monitoring Platform Usage

Organization administrators can monitor current usage via Atlassian Administration:

The relevant section can be found at:

Atlassian Administration → Insights → Platform usage

Depending on your role and permissions, you can view the following information there, among other things:

• The total allocated quota
• Current usage
• Usage trends at the app level
• Individual user usage
• Features that place a particularly heavy load on the quota

Administrators should review usage before December 3, 2026, set realistic limits, and actively monitor notifications at 80% and 100%. This will help prevent unexpected costs and service interruptions.

Our Conclusion

Starting December 3, 2026, Atlassian will track certain usage at the organizational level and bill for additional usage based on the feature. This includes, among other things, Rovo credits, automation steps, Assets objects, Bitbucket metrics, and solutions provided by AI agents.

It is therefore important for companies to review their own quotas, usage limits, and billing options well in advance. Central management is handled through Atlassian Administration. There, organization administrators can monitor platform usage and determine whether additional usage should be allowed or restricted.

Would you like to proactively manage the new usage quotas and costs for your Jira and Atlassian environment? We’d be happy to assist you in reviewing your current usage, setting reasonable limits, and preparing for usage-based billing starting in December 2026. Contact us for a no-obligation consultation.