Atlassian pricing changes 2026: what changes on 3 December

Atlassian is expanding usage-based pricing alongside its seat subscriptions, with billing for most meters starting on 3 December 2026. For Jira and Confluence teams, the main questions are how much automation and Rovo usage the plan includes, and what happens at the limit. A team that stays within its allowance will not incur extra usage charges. A team that exceeds it may pay more or have metered features stop, depending on its settings.

Atlassian's 1 September announcement names Jira, Confluence, Jira Service Management and Rovo. It also covers changes to Assets and Bitbucket. Trello is not named among the affected products.

Disclosure: We make Breeze, a project management tool that overlaps with Jira for some teams. The pricing and billing rules below come from Atlassian's linked pages.

Contents

• What changes in December?
• What does Jira cost per user?
• A 25-user budgeting example
• What do the usage meters count?
• What is included without extra charges?
• Is Trello included?
• How should you prepare?

What changes on 3 December 2026?

The change adds a usage layer to existing subscriptions. Seats still determine access, while metered capabilities have allowances and rules for additional usage. Those allowances depend on the product and plan. On Jira, each paid user adds 25 Rovo credits a month on Standard, 70 on Premium and 150 on Enterprise, plus 400, 750 or 1,000 automation steps, all pooled across the organization. From 3 December 2026, use beyond the allowance is billed at $0.01 per Rovo credit and $0.50 per 1,000 automation steps.

Atlassian's usage pricing overview now links to published rate cards, support documentation and an estimator. Check the meters your organization uses rather than treating the December change as a fixed percentage increase.

Two teams with the same seat count can have different usage costs. For example, a rule that runs occasionally may use little of an allowance, while a flow triggered by every work-item update can run many times. The relevant question is how many billable steps execute, not how many rules exist.

What does Jira cost per user?

The Jira pricing page sets the per-user rate by team size. On monthly billing, teams of 1 to 100 users pay the US dollar rates below. Use its calculator for your user count and billing term; multiplying a per-user price is an illustration, not an annual contract quote.

Per-user rates fall as the team grows. The pricing page opens on a 300-user example, where Standard is $7.91 and Premium $14.54 per user per month, so those lower figures are not what a small team pays. Annual billing is priced per user tier rather than per user: for 1 to 10 users it is $900 a year for Standard and $1,850 for Premium.

The usage announcement is separate from your seat-price calculation. It does not establish a permanent price guarantee or replace your renewal terms. Confluence and service-management subscriptions also have their own base prices.

How would the change affect a 25-user team?

At the monthly rates for teams of up to 100 users, a simple 25-user multiplication gives a base of $226.25 for Standard or $457.50 for Premium per month, before tax and other products. Confirm the actual subscription total in your quote.

Atlassian's automation usage rules set extra usage at $0.50 per 1,000 steps, billed from 3 December 2026. If the Standard example uses 20,000 steps, has no other pooled allowance and enables extra usage, the excess is 10,000 steps, or $5. Rovo is a separate meter: if the same team used 1,625 Rovo credits in a month, the 1,000 beyond its 625 would cost $10 at $0.01 each.

This example isolates one meter so the arithmetic is clear. A real organization may receive allowances from several subscriptions. Use the organization total rather than assigning the same shared allowance to each team's budget.

What do the usage meters count?

Rovo credits

Rovo credits cover billable AI interactions and some Teamwork Graph context requests. Paid Jira plans include 25 credits per user per month on Standard, 70 on Premium and 150 on Enterprise. Confluence has the same allowances, and Service Collection and Teamwork Collection include 250, 700 and 1,500. Jira Free has no Rovo allowance. Credits are pooled across the organization, reset monthly and do not roll over.

The Rovo credit rules distinguish basic interactions from more demanding agents and models. A basic event, such as a quick Rovo Chat answer, costs 10 credits. Premium features such as Think deeper, Agents in Jira and the Jira Coding Agent use a variable number of credits, and Atlassian publishes no fixed rate for them, so one chat message is not a reliable unit for budgeting every Rovo workflow.

From 3 December 2026, use beyond the allowance costs $0.01 per credit, or $10 per 1,000. Extra usage is switched on by default; admins can set a spending cap or turn it off, and get alerts at 80% and 100% of the allowance. Enriched context calls made by tools such as Claude or ChatGPT through Atlassian's Rovo MCP server or the Teamwork Graph CLI also use credits, while single-product lookups and writes are free.

Automation steps

Jira includes 150 automation steps per subscription per month on Free, then 400 per user on Standard, 750 on Premium and 1,000 on Enterprise. Confluence allowances are smaller: 100, 250 and 500 per user on its paid plans. Steps are pooled across the organization.

Triggers, conditions, actions, branches and loops count when they execute, including a trigger that finds no match. A flow can therefore consume several steps per run. Agentic actions such as Use Rovo or the Jira Coding Agent are billed as Rovo credits instead of steps. With extra usage disabled, reaching the allowance stops flows until the usage billing date resets it. With extra usage enabled, flows continue and, from 3 December 2026, the excess is billed at $0.50 per 1,000 steps.

AI agent resolutions

This meter counts qualifying requests resolved by an AI agent. The resolution billing documentation covers Customer Service Management. Service teams should check the product and agent they use rather than assume every chatbot interaction is a resolution.

These are not the only capabilities covered by the rollout. Assets objects and Bitbucket have their own rules. If your organization uses them, include those costs in the same review.

What is included without extra usage charges?

Included usage is part of the subscription rather than a separate charge. Some Rovo features, including embedded summaries and Rovo Search in Atlassian apps, are classified as free. That does not mean every search or AI interaction through every integration is free.

Free plans also have usage limits. For example, Jira Free includes 150 automation steps per subscription per month. A $0 subscription is not evidence that usage cannot be measured or restricted.

Is Trello part of this pricing change?

Trello is not named among the affected products in the 1 September announcement, and it is not among the apps on Atlassian's usage billing page. There is no basis for applying these Jira and Confluence usage charges to a Trello workspace. Trello meters automation in Workspace command runs instead: 250 a month on Free, 1,000 on Standard and unlimited on Premium. Its AI features are included from the Standard plan, $5 per user per month billed annually, with no credits, and its MCP server is available on every plan including Free.

If that difference is what has you weighing the two against each other, Jira and Trello compared on plans and limits covers where each one stops, including what both still include free for up to ten people.

How do you estimate usage before committing to a budget?

Use a representative period rather than the quietest week you can find. A project launch, bulk import or monthly reporting cycle may produce more automation activity than ordinary task updates. Record those events beside the usage figures so you can distinguish normal growth from an unusual spike.

For each important workflow, write down the trigger, how often it fires and the actions it performs. A flow that runs for every edited work item has a different cost profile from one that runs only when an approval is complete. Branches and loops can also make the number of steps vary between runs.

Consider a team that copies status changes into several linked records. The flow may be useful, but an edit to one of those records could trigger more work. Review the actual execution history before estimating its cost from the number of visible rules. Removing a duplicate trigger can reduce usage without removing a useful outcome.

Keep the operational decision separate from the arithmetic. A low-cost flow might send a critical handoff notification, while a high-volume flow might produce a report nobody reads. Review the value of the output with its owner before disabling either one.

Should you buy extra usage or move to a higher plan?

A larger allowance is only one part of a plan upgrade. In the 25-user example, the seat-price difference between Standard and Premium is $231.25 per month. The illustrated 10,000 extra automation steps cost $5. On those assumptions, upgrading only to avoid that automation charge would cost more.

That does not establish Standard as the better plan for every team. Premium may include planning or administration features you need independently of usage. Compare the complete package with your actual requirements, and use your subscription quote for the final calculation.

Also check whether the organization has other subscriptions contributing to the allowance. An individual team may appear over its share while the organization remains within the pooled total. Assigning each team the entire pool would produce the opposite problem: budgets that look affordable separately but exceed the available usage together.

For a recurring review, keep four figures together: the seat subscription, included usage, expected additional usage and the setting that controls what happens at the limit. Record who can change that setting. This makes a later billing question easier to resolve than a spreadsheet containing only a per-user price.

If a workflow must stop at a spending limit, document how the team will handle the affected work. For example, someone may need to review an intake queue manually until the allowance resets. Treat that fallback as part of the operating cost, alongside any usage charge.

What should you do before December?

Start with the usage that supports important work. Identify who owns each flow or agent and what would happen if it stopped. Then compare the value of that work with the relevant allowance and rate.

• Review usage by meter. In Atlassian Administration, compare recent usage with the organization allowance. Rule-run counts alone do not show executed steps.
• Choose what happens at the limit. Decide where a spending limit is appropriate and where stopping an important workflow would cost more than additional usage.
• Assign someone to alerts. Make sure a named admin can respond before a limit interrupts work.
• Remove unnecessary runs. Check duplicate flows, frequent schedules and triggers that run when no useful work is needed.

If the cost still outweighs the benefit, compare the workflow with Jira alternatives. A simpler board may suit straightforward task coordination. Teams that depend on Jira's development workflows and integrations should include the work of replacing them in the decision.

Budget for the workflow you actually use

The useful comparison is your subscription plus measured usage, with the settings you intend to keep. Review a representative month, allow for expected growth and test what happens at the limit. That gives you a more useful budget than assuming every small team will stay under the allowance.

Written by Lucas

Lucas writes content at Breeze and specializes in project management, team collaboration, and practical workflow advice. He helps small teams and growing businesses plan projects, track progress, and keep work organized by sharing clear, actionable guides.