Upcoming changes to Rovo Dev

Code Reviewer will be available with your eligible Jira/TWC subscription, with no separate Rovo Dev license required. It will operate under Atlassian’s Usage-Based Pricing (UBP) model as part of the Jira/TWC subscription. It will continue operating in existing SCM workflows, with more integrations coming to Jira.

Code Reviewer will transition to Rovo Credits on December 3, 2026.

No action is required today. Continue using Code Reviewer as usual.

More details:

• Access & continuity: Code Reviewer will be available to you if you have a paid Jira subscription, with no separate Rovo Dev license required. The developer review experience will remain unchanged. Automated reviews will continue to run on pull requests as before. Existing settings and configuration will be preserved.

• Administration & configuration: Code Reviewer settings will be available through Jira Settings; GitHub customers will configure Code Reviewer in Jira; Bitbucket Cloud customers can continue configuring Code Reviewer in Bitbucket Cloud as they do today.

• Pricing & Rovo Credits: Starting December 3, 2026, Code Reviewer usage will be measured using Rovo Credits under Atlassian’s Usage-Based Pricing model and subject to our Acceptable Use Policy. Detailed admin guidance and usage dashboards will be provided well in advance.

• Subscription guidance: we will not automatically cancel your Rovo Dev subscription. We’ll tell you when your transition path is ready and when it is appropriate to make changes to your subscription.

  • If you only use Code Reviewer, we will notify you when it is live in Jira so you can comfortably cancel your Rovo Dev subscription.

  • If you also use CLI or IDE features: Keep your Rovo Dev subscription active until those tools complete their transition paths.

Rovo Dev CLI is evolving into the unified Atlassian Rovo CLI experience, which will operate under Atlassian’s Usage-Based Pricing model after the transition.

No action is required today. Continue using Rovo Dev CLI until migration instructions are shared.

We will provide step-by-step migration documentation, prerequisites, and a generous transition window before the legacy CLI is retired.

Standalone Rovo Dev IDE capabilities will be retired. Standard Jira and Bitbucket extensions such as AtlasCode are unaffected.

No action is required today. Continue using your setup until retirement dates are confirmed. You will receive advance notice before any standalone IDE capabilities are discontinued.

While standalone Rovo Dev IDE capabilities will be retired in the coming months, standard Jira and Bitbucket extensions such as AtlasCode will continue to be fully supported and maintained.

October 1, 2026 - All Rovo Dev tools, including Code Reviewer, remain active.

December 3, 2026 - Code Reviewer begins operating under Atlassian’s Usage-Based Pricing model as part of the Jira/TWC subscription. Note: December 3, 2026 is the planned start of Rovo Credits enforcement for Code Reviewer in Jira. It is not the Rovo Dev end-of-life date.

Upcoming (Dates TBA)

• Code Reviewer is available with an eligible Jira/TWC subscription.

• Rovo CLI migration: Step-by-step guides and timeline for moving to Rovo CLI.

• IDE retirement: Advance notice before standalone IDE features are phased out.

• Rovo Dev End of Life: Final end-of-life date for Rovo Dev.

No. All active Rovo Dev capabilities, including automated code reviews on connected repositories, continue to work normally throughout the transition period.

We will notify primary account contacts via email and update this page whenever a milestone date, migration guide, or capability schedule is published.

Code Reviewer is moving from Rovo Dev to your eligible Jira and Teamwork Collection subscriptions. With this transition, Code Reviewer will operate on Rovo credits under our usage-based pricing model starting December 3, 2026.

Each code review it performs uses Rovo credits from your organization's allowance, the same pool used by other Rovo features such as Rovo Chat and agents.

Code Reviewer triggering schedules depend on your settings. Here are the options available:

• Only when a pull request is created: Code Reviewer runs automatically when a pull request is created, but not for subsequent commits.

• When a pull request is created, and on each commit: Code Reviewer runs automatically when a pull request is created and whenever a new commit is made.

• Don’t review automatically: Code Reviewer only runs when the author starts it manually (the default option).

We recommend starting with “Only when a pull request is created” so Code Reviewer can scan every new pull request to provide timely feedback.

(Learn more about triggering: Trigger a Code Review )

Each review uses a variable number of credits, based on how much work Code Reviewer does to understand and review the change. Reviews generally use more credits when:

• The pull request is larger: more files and lines changed mean more code to read and review.

• Reviewing frequent new commits in pull requests: when the schedule is set to trigger on each commit, new commits will trigger another review, keeping feedback up to date.

• Code Reviewer reads more of a large repository: It looks beyond the diff to understand related code in the codebase to deliver accurate feedback. In larger codebases, this means more work for the Code Reviewer.

• Sizes of Custom Instructions, Agent Skills or Code Standards: these features make reviews more specific to your team and use additional credits because Code Reviewer will ingest additional context.

(Learn more about Custom Instructions or Code Standards)

Rovo credits are pooled across your organization, so the number of reviews you can run depends on how many users you have under the subscriptions and how much your teams use other Rovo features.

If nothing else was using credits, your monthly allowance would typically cover the following:

These ranges are estimates, not guarantees. Smaller, focused pull requests sit toward the higher end of each range, and large or frequently updated pull requests toward the lower end.

Credits used by other Rovo features reduce the number of reviews available.

• Keep pull requests focused: smaller pull requests are cheaper to review and easier for your team to approve.

• Choose where automatic review runs: turn it on for the repositories where it adds the most value.

• Keep instructions and standards concise: they are what make reviews accurate for your team, so keep them rather than removing them, but trim outdated or overlapping guidance.

Organization admins can view Rovo credit usage, including usage by feature, in Atlassian Administration. To learn about allowances, extra usage and what happens when your organization reaches its limit, see How Rovo credits work.

For developers, there’s no change. Code Reviewer will continue to review pull requests and provide feedback as it does today.
For administrators:

• Jira administrators will be able to manage Code Reviewer directly in Jira Settings, including repository enablement and triggers.

• Bitbucket Cloud administrators can continue configuring Code Reviewer in Bitbucket Cloud as they do today.

• GitHub administrators will be able to configure Code Reviewer in Jira Settings.

Yes. Your active repository connections, review rules, custom instructions, and setup will remain intact, so developers experience continuous, uninterrupted reviews.

When Code Reviewer becomes available to you in Jira, you can use it without Rovo Credits metering during the transition window leading up to December 3, 2026. This allows your team to establish workflows and evaluate usage. Starting December 3, 2026, usage will be metered via Rovo Credits under our Usage-Based Pricing model.

Starting December 3, 2026, Code Reviewer will transition from the standalone Rovo Dev license to Rovo Credits under Atlassian's Usage Based Pricing. Your use of Code Reviewer with Jira is subject to Atlassian’s Acceptable Use Policy. Detailed admin guidance will be provided to help your team monitor and manage credit consumption.

Atlassian will not automatically cancel your Rovo Dev subscription. You can continue using Rovo Dev as you do today, please follow the transition path below for each capability.

• Code Reviewer-only users: Once Code Reviewer is available to you in Jira, we will notify you so you can comfortably manage or cancel your Rovo Dev subscription in the billing portal.

• CLI and IDE users: Please keep your Rovo Dev subscription active until the transition paths and instructions for those capabilities are released.

Your investment and prepaid term are fully protected. Our teams are working to ensure a fair commercial transition for all annual customers. If you have an active annual subscription, a recently renewed subscription, or have questions about cancellation or commercial adjustments, please contact Atlassian Support.

No. Standard developer integrations and extensions, such as AtlasCode (for Jira and Bitbucket) and SCM repository connections, are not affected and remain fully supported. Only Rovo Dev IDE features are being retired.

Standard Bitbucket Pipelines (CI/CD builds, tests, and deployments) are completely unaffected.

If you currently use Rovo Dev CLI to run agentic pipelines in Bitbucket:

Bitbucket Pipelines will provide a transition to Rovo CLI once it's available. Until then, Rovo Dev CLI will be supported.