Webinar Q&A: Rovo Dev in Jira

[#1]

Thank you for joining our webinar Rovo Dev ships the small tasks while you tackle the cool stuff. If you missed it, you can watch it on demand.

Those who attended live shared many thoughtful questions. We heard strong in topics ranging across setup, pricing, integration, automation security, and how Rovo Dev in Jira can help with your day-to-day work.

We weren’t able to answer every single question, but we’ve pulled together the most common questions and answers below to help you better understand what Rovo Dev in Jira can do, how to get started, and how to go deeper on a specific topic.

Please leave any follow-up questions in the comments below, and we’ll get back to you.

Getting started and access

Q: What setup is required to use Rovo Dev in Jira?

Customers need Rovo Dev added to their site to use Rovo Dev in Jira. Additionally, Rovo Dev in Jira needs to be enabled at both the site and organization level, there need to be available Rovo Dev credits, and Bitbucket Cloud or GitHub Cloud needs to be connected to the Jira site.

Additional details can be found here.

Q: Is Rovo Dev in Jira generally available, or still in beta / early access?

Rovo Dev in Jira is in GA rollout, meaning it is not simply an invite-only beta experience. While being rolled out, Rovo Dev in Jira may not be visible to every eligible customer yet. Depending on rollout timing and site setup, some customers may already have access, while others may still be waiting for enablement.

To turn Rovo Dev in Jira on/off, please read these instructions.

Q: Why can some customers use Rovo Dev CLI but not yet see the full Rovo Dev in Jira experience?

Access to the Rovo Dev Cli does not automatically mean Rovo Dev in Jira is enabled. Rovo Dev in Jira has its own rollout and enablement requirements, including site/org enablement and the necessary Jira + source code management connections. So a customer may already have access to CLI, but still not have the Jira experience turned on or rolled out yet.

Q: What permissions are required for Rovo Dev to create branches, commits, and pull requests?

Rovo Dev in Jira needs the appropriate access to the connected source code system in order to create branches, commits, and pull requests. A Jira site must be connected to Bitbucket Cloud or GitHub Cloud, and the environment must have the necessary permission/tool access to perform those actions.

If Rovo Dev is configured to commit code to a branch and create a draft pull request, it won’t merge the draft pull request directly, but will hand it back to your team for review and merge.

Pricing and Credits

Q: How does Rovo Dev pricing work, and is it included in any existing Atlassian plans?

Rovo Dev uses a seat + usage-based pricing model with credits. Customers can purchase Rovo Dev seats for individual developers who need them without having to purchase seats for an entire organization. Plan details (structure and overages pricing) are available on the Rovo Dev Pricing page.

Rovo Dev is a separate product from other existing Atlassian plans, like Jira and Bitbucket.

Q: How does Rovo Dev’s credit model work?

Rovo Dev uses a per-user credit usage model layered on top of seat-based pricing. Credit allowances are allocated per user and are not pooled org-wide. The Rovo Dev Standard plan is priced at $20 per user per month and includes 2,000 credits (overages are billed at $0.01 per credit).

Q: Do Rovo Dev in Jira and Rovo Dev CLI consume the same credit pool?
Yes, Rovo Dev in Jira and Rovo Dev CLI draw from the same underlying Rovo Dev credit pool. Rovo Dev in Jira generated code use the same credits as the Rovo Dev CLI, plus one additional credit for use of the cloud-based sandbox.

Integrations and supported tools

Q: Which source code platforms does Rovo Dev in Jira support today?

Today, Rovo Dev in Jira supports Bitbucket and GitHub Cloud.

Q: Is GitLab support planned, including self-managed GitLab?

GitLab, including self-managed GitLab, is not supported today, and there is no timeline for making Rovo Dev compatible with GitLab.

Q: Does Rovo Dev work with Azure DevOps repositories and pipelines?

We currently support Bitbucket Cloud and GitHub Cloud. Rovo Dev does not currently support Azure DevOps repositories and pipelines. Supporting Azure DevOps is included in our Rovo Dev development roadmap.

Q: Will Rovo Dev work with Jenkins, Bamboo, or other external CI/CD tools?

Rovo Dev can fit into workflows that use external CI/CDs tools depending on how those tools are connected. For example, Rovo Dev code review runs in the PR screen in Bitbucket Cloud. If you’re using Bitbucket Cloud with Jenkins, you can still use Rovo Dev to run your reviews. Rovo Dev also has a feature to debug build failures (note, this is available only in Bitbucket Pipelines).

Context and Customizations

Q: How does Rovo Dev in Jira understand enough context from a single Jira ticket to generate useful code?

Rovo Dev does not rely only on the text of a single Jira ticket. It draws on both your work item and broader context in Jira and Confluence that the initiating user can access, as well as the selected repository for the session. The more complete and well-connected the surrounding project information is, the better Rovo Dev can perform.

Q: What context does Rovo Dev use from Jira, Confluence, repositories, and pull requests?

Rovo Dev in Jira runs in a secure, cloud-based coding session inside a dedicated sandbox environment. It acts on behalf of the initiating user and can only access data and perform actions that the user already has permission to access.

It can create, read, update, and search in Jira and Confluence (but not delete), and it can read from and write to the repository selected for the session. It can also run Bash or PowerShell commands in the sandbox. It does not copy data from other repositories or a user’s local file system, does not merge pull requests, and does not connect to third-party data sources via MCP.

Q: Can users provide specific instructions or default guidance for how Rovo Dev should work on tasks?

Yes, users can provide additional instructions and relevant information when configuring a Rovo Dev in Jira session. Instructions on how to configure a Rovo Dev in Jira can be found here.

Q: Are there best practices for writing Jira tickets or Confluence pages so Rovo Dev performs better?

Context quality matters. Teams should provide as much clear, relevant context as possible in Jira and linked documentation so Rovo Dev can better understand the task.

Workflow, automation, and code review

Q: What actually happens when a user starts a Rovo Dev session from Jira?

When Rovo Dev in Jira is enabled, a Rovo Dev section appears on the work item. From there, a user can select Code this task for me to start a secure, cloud-based coding session in a dedicated sandbox environment. Rovo Dev works against the selected repository for the session and can optionally push code changes to a branch and create a draft pull request.

Q: How do you use Rovo Dev for code review in Bitbucket pull requests?

Rovo Dev supports code review in Bitbucket pull requests. You can find setup and additional details here.

Q: Can Rovo Dev be triggered from Jira automation rules?

Yes, Rovo Dev can be used in Jira automations. You can configure automation rules to trigger Rovo Dev actions as part of your workflow. Follow the instructions here.

Q: Can Rovo Dev help generate tests, review code quality, and remediate vulnerabilities?

Yes, Rovo Dev can help generate tests, support code review workflows, and assist with vulnerability remediation. At Atlassian, Rovo Dev has helped resolve 51% of open security vulnerabilities.

Read more about how we are using Rovo Dev at Atlassian:

• How We Turned Feature Flag Cleanup Into a Mostly‑Hands‑Off AI Workflow
• Delivering 120 PRs in two weeks with Rovo Dev in Jira

As with any generated code, teams should review and validate the output before merging.Security

Q: How does Rovo Dev handle security, privacy, and intellectual property concerns?

Rovo Dev in Jira runs in a secure, cloud-based sandbox and acts on behalf of the initiating user. It can only access data and perform actions that the user already has permission to access. It works only with the selected repository for the session, does not copy data from other repositories or a user’s local file system, does not merge pull requests, and does not connect to third-party data sources via MCP. Teams remain responsible for reviewing, approving, and merging any generated code.

Q: Which AI models does Rovo Dev support today, and can customers choose among them?

By default, Rovo Dev in Jira uses Claude Sonnet 4.6.

Thank you for joining our webinars and the lively discussion. Your questions, interest, and feedback help us improve Rovo Dev so you can get more from it.

If you want to try Rovo Dev, you can sign up here.