RRovo Agents by Atlassian

Atlassian will start billing for Rovo usage past the included allowance on December 3, 2026, and the allowance on a Jira Standard seat is 25 credits a month. At 10 credits per basic agent run, that covers about two and a half runs per person, pooled across the organization. Extra credits cost $0.01 each. Rovo is the AI layer Atlassian has built into Jira, Confluence and Jira Service Management: agents that can be assigned work items, a chat assistant and search across team knowledge.

Rovo is best for teams already running projects in Jira and Confluence, because it needs no new tool and works on data those teams already keep. The credit meter is the main planning point: allowances on Standard plans are modest, and premium features such as Think Deeper and advanced agents use a variable number of credits. Access comes with paid Atlassian cloud plans rather than a separate seat, and we rate Rovo 8.9/10 on our scale. We have not used Rovo ourselves; this review is based on Atlassian’s published documentation, pricing notes and financial results.

Allowances, Meters and Atlassian’s Financial Results

Atlassian does not publish Rovo usage figures on their own, but its pricing documents and financial results give buyers a clear picture of the allowances, the meter and the scale of the business behind the product.

The allowance table matters more than any headline figure. A 25-credit seat is a taster, not a working budget, for any team that wants agents running every day. The collections are where Atlassian has put the real volume: a Teamwork Collection seat on Standard carries ten times the credits of a Jira Standard seat.

The 1 million monthly users of the MCP server and CLI point to the other half of the strategy. Atlassian is positioning Jira and Confluence as the shared context for many agents, its own and other vendors’, and Rovo credits as the toll for the richer cross-product lookups.

Agents Working on the Teamwork Graph Inside Jira

Rovo is not a separate app. It appears inside Atlassian cloud products and works on the data those products already hold, which Atlassian calls the Teamwork Graph: work items, pages, comments, people and the links between them.

Agents on Jira Work Items

According to Atlassian’s Jira documentation, teams can collaborate with Rovo agents or other AI agents directly on work items in company-managed and team-managed spaces. There are three ways in: assign a work item to an agent, @mention an agent in a comment, or trigger an agent when work moves through a workflow transition. Adding an agent to a work item sets up a two-way interaction, so the agent reads the item and posts its results back where the team can see them.

Agents do not have to come from Atlassian. The documentation set includes pages on Claude Agent for Jira and on using third-party coding agents in Jira automation, and Atlassian Studio covers creating and editing custom Rovo agents. Write operations through the Rovo MCP server, such as updating a Jira work item, are free of credits.

Chat, Search and Specialist Agents

• Rovo Search: searches across Atlassian apps at no credit cost.
• Rovo Chat: Quick Answers for everyday questions at 10 credits per message, and Think Deeper for multi-step reasoning at a variable cost.
• Jira Coding Agent: a premium agent for development work, billed in variable credits.
• Request Resolver: a service agent for Jira Service Management; Atlassian says its users resolve issues 13% faster than non-AI users.
• Embedded AI: summaries, definitions and rewrites inside the apps stay free.

Admin Switches, Verified Domains and First Agents

• Enable: a site admin turns on Rovo, AI features or MCP agents, and enables Rovo and Jira AI on the site. The Rovo admin must use a verified business domain.
• Choose agents: decide which Atlassian, custom or third-party agents teams can add to work items.
• Wire into workflows: attach agents to transitions where a step is repeatable, such as triage or drafting a first response.
• Set limits: decide whether extra usage stays on, set a spending cap and watch the 80% and 100% alerts.

Reviewing Agent Posts and Choosing Triggers

Atlassian’s documentation warns that the quality, accuracy and reliability of AI-generated information may vary. Teams still review what agents post, decide which transitions should trigger them and keep Confluence pages current. G2 reviewers make the same point: answers are only as good as the underlying documentation.

Credits in the Subscription, Then Extra Usage

Rovo is paid for through credits included in Atlassian cloud subscriptions, then through extra usage. The figures below are from Atlassian’s support documentation, which applies the current table to all usage from August 31, 2026.

Billable events fall into tiers. Free features include Rovo Search, definitions and summaries. Basic features cost 10 credits per event, covering Quick Answers, Rovo space creation and basic agents without model selection. Premium features cost a variable number of credits, covering Think Deeper, advanced agents with model selection, Confluence slides, the Jira Coding Agent and Request Resolver. Cross-product Teamwork Graph lookups through the CLI or MCP server mostly cost 1 to 10 credits per call. Beta features do not count against the allowance unless Atlassian says otherwise.

Credit Math for Twenty Users on Standard

These scenarios use Atlassian’s published allowances and the $0.01 list price, and assume basic 10-credit events only. Usage levels are our own illustrative assumptions.

• A 20-person team on Jira Standard: the pooled allowance is 500 credits, enough for 50 basic agent runs. If the team runs 300 a month, that is 3,000 credits, and the extra 2,500 cost $25.
• A 100-person team on Jira Premium: the pool is 7,000 credits. Three basic events per person per working day over 21 days is 6,300 events, or 63,000 credits; the extra 56,000 cost $560 a month.
• A 50-person team on Teamwork Collection Standard: the pool is 12,500 credits. The same three events a day comes to 31,500 credits, leaving 19,000 extra at $190 a month.

Premium features change the picture, because Atlassian prices them by reasoning steps, searches, tools and model power rather than a flat rate. A team that leans on Think Deeper or the Jira Coding Agent should treat the basic scenarios as a floor. Automation steps and AI agent resolutions are separate meters with their own allowances, so a workflow that mixes automation rules and agents can draw on more than one.

Rovo Compared With Asana AI Teammates, ClickUp Super Agents and monday.com AI Agents

The main project management suites have all added agents in 2025 and 2026, and all four now charge through some kind of credit or request meter. The difference is where each meter starts and how much is included.

Rovo wins on depth for teams whose work already lives in Jira: agents act on the same work items, workflows and Confluence pages, and outside agents can join through MCP. Asana and ClickUp suit teams outside engineering, and monday.com gives business teams more outside channels such as WhatsApp and Gmail. Compare more options in our AI agents for project management and IT and DevOps guides.

Jira Software Teams and Service Desks

• Software teams on Jira Cloud: agents can take assigned work items, and the Jira Coding Agent and third-party coding agents plug into the same backlog.
• Service desks on Jira Service Management: Request Resolver is built for service work, and the Service Collection carries ten times the per-app credits.
• Organizations with large Confluence knowledge bases: Rovo Search and Chat draw on pages teams already maintain, and search is free.
• Teams building their own agents: the MCP server and CLI let outside agents read and update Jira and Confluence, with write operations free of credits.
• Healthcare-adjacent teams: Atlassian added Rovo to its HIPAA-covered apps.

Teams Off Atlassian Cloud or Needing Larger Allowances

• Teams not on Atlassian cloud: Rovo only works with Atlassian cloud products.
• Small teams on Standard plans expecting heavy agent use: 25 credits per user goes quickly at 10 credits a run, so extra usage becomes the real price.
• Buyers who need a fixed AI budget: premium features use variable credits that depend on reasoning steps and tools.
• Business teams that run work outside Jira: a tool such as monday.com or Asana may fit their boards and workflows better.
• Teams with sparse or outdated documentation: reviewers say answer quality depends on how well source pages are kept.

Set a Spending Cap Before December 3, 2026

• Extra usage is on by default: once billing starts on December 3, 2026, features keep running past the allowance until a spending cap is hit. Set one first.
• Variable premium costs: Think Deeper and advanced agents are priced by reasoning steps, search volume, tools and model, which makes forecasts rough.
• Several meters: Rovo credits, automation steps and AI agent resolutions are separate meters, so check all three for workflows that combine them.
• No rollover: unused credits reset each month, and prepaid packs are the only way to buy ahead.
• Beta features may become billable: beta AI features are free until generally available, then may count against the allowance.
• Early public reviews: G2 had six reviews when we checked, so user sentiment is an early signal rather than a settled view.

Three Usage Meters Announced for Atlassian Cloud

• On September 1, 2026, Atlassian announced expanded usage-based pricing with three meters, Rovo credits, automation steps and AI agent resolutions, taking effect December 3, 2026.
• On August 6, 2026, Atlassian reported fiscal fourth quarter results with revenue of $1,766 million, up 28%, and said its MCP server and Teamwork Graph CLI had reached 1 million monthly active users.
• Atlassian’s credit documentation applies the current pricing table to all usage and forecasts from August 31, 2026.

Jira and Confluence Teams Gain the Most From Rovo

For teams already on Jira and Confluence, yes. Rovo scores 8.9/10 on our scale, with its best marks for integrations and autonomy. Agents that can be assigned work items and triggered by workflow transitions fit how Jira teams already work, and the open MCP surface means Rovo is also the shared context for other vendors’ agents.

Budgeting is the area to plan most carefully. A Standard seat covers a couple of basic agent runs a month, and premium features use a variable number of credits. In our 100-person Premium scenario, modest daily use adds about $560 a month in extra credits. Before December 3, 2026, set a spending cap, watch real usage for a month and decide whether a collection plan or a prepaid pack is cheaper than paying as you go.

Credit Allowances per Jira Seat, Answered

How Many Rovo Credits Does a Jira Standard Seat Include?

Each Jira Standard user adds 25 credits a month to an organization-wide pool. Premium adds 70 and Enterprise 150. Unused credits reset monthly and do not roll over.

Is Rovo Free on the Jira Free Plan?

Atlassian’s credit documentation lists allowances only for paid Jira, Confluence, Service Collection and Teamwork Collection subscriptions. Embedded features such as Rovo Search and summaries do not use credits on paid plans.

What Happens When Rovo Credits Run Out?

From December 3, 2026, extra usage is billed at $0.01 per credit if it is switched on, which it is by default. Admins can set a spending cap or turn extra usage off, in which case billable features pause until the allowance resets or more credits are bought.

Can Non-Atlassian Agents Work on Jira Work Items?

Yes. Atlassian’s documentation covers Claude Agent for Jira and third-party coding agents run through Jira automation, and the Rovo MCP server lets outside tools read and update Jira. Cross-product lookups through the MCP server or CLI mostly cost 1 to 10 credits per call.

How Does Rovo Compare With Asana AI Teammates?

Both are built into their parent platforms. Rovo includes 25 to 150 credits per user on Jira and Confluence plans with $0.01 extra credits, while Asana includes five AI requests per user with extra requests at $0.50 to $0.60. Rovo is the stronger fit for software and service teams; Asana for cross-functional project work.