Enabling Rovo in Bitbucket and How it Relates to Jira and Data Privacy?

[Ben]

We would like to enable Rovo (search, chat, but especially Code Reviewer) in Bitbucket. Our team is responsible for administering Bitbucket and getting any necessary approvals for enabling features and the data residency, privacy, etc that goes along with it. However, another team in the organization has those same responsibilities for Jira / Confluence.

The last step before enabling Rovo Dev Agents (to enable Code Reviewer) in Bitbucket is this screen (below).

It is unclear to me how Dev Agents in Bitbucket tie into Jira and where the data "flows". Do the prompts and other data flows go "through" Jira and do the Jira data policies apply? Is it all one big Atlassian 'bucket' that all of this lives in from a policy perspective including Bitbucket? How does this all tie together?

Our org has already enabled Rovo for Jira / Confluence so perhaps some of the data residency / privacy stuff is already accounted for but it's unclear to me if Bitbucket and the Rovo Dev Agents differ and what we might need to investigate from the data perspective. Do they differ from in intelligence in Jira / Confluence in terms of what they send to 3rd party LLMs?

I have read https://www.atlassian.com/trust/atlassian-intelligence but it still seems a bit nebulous and unclear to me when it comes to the Rovo Dev Agents specifically.

[Jovana Dunisijevic]

Hi @Ben 

First off! Apologies you haven't heard back from anyone in 3 weeks! I just got back from my PTO and am catching up to all the requests!

Let me try to address all your questions now!

To answer the data flow question: When you use Rovo Dev Agents in Bitbucket, relevant data (such as code snippets, pull request metadata, and sometimes linked Jira issues) is sent to Atlassian’s AI services for processing. The data does not “flow through” Jira—rather, the integration allows the agent to access context from both products as needed. The data policies for both Jira and Bitbucket apply, but there is no cross-product data sharing beyond what’s required for the agent to function.

The way it does data handling:  Rovo Dev Agents send only the minimum necessary code snippets and metadata to third-party large language model (LLM) providers to generate responses. No customer data is retained by these LLMs, and your data is never used to train their models or shared across customers. Each request is sent over SSL-encrypted channels, and LLM partners have a strict zero data retention policy.

Also, Data residency for Rovo is now available in limited release, with broader support rolling out this year. This means you can pin your Rovo data (including agent configuration and indexed content) to the same region as your Jira/Confluence data, supporting your organisation’s compliance requirements.

Both Rovo Dev Agents and Atlassian Intelligence use the same secure AI infrastructure and LLM partners. If your organization has already approved Atlassian Intelligence, there are no additional privacy or security concerns for enabling Rovo Dev Agents.

If you’ve already enabled Rovo for Jira/Confluence then many of your privacy, data residency, and compliance requirements are already addressed. Enabling Rovo Dev Agents in Bitbucket will follow the same standards and policies. 

Now to make sure you have it in Bitbucket as well, ensure your workspace is on a Standard or Premium plan, connected to a paid Jira site (which I believe this is already done). You can then activate Code Reviewer and other agents at the workspace or repository level. You need to have admin permissions for the workspace or repository to enable this.

I believe you're only missing these steps:

Enable Rovo Dev Agents at the Workspace Level (Workspace Admin)

1. In Bitbucket, go to Workspace settings.

2. Find the Rovo Dev Agents section (under Atlassian integrations).

3. Enable the Rovo Dev Agents feature for the workspace.

   • If prerequisites aren’t met, you’ll be directed to AdminHub for setup 1 2.

Enable Code Reviewer at the Repository Level (Repository Admin)

1. In Bitbucket, go to the repository settings for each repo you want to enable the agent on.

2. Find the Code Reviewer setting and toggle it ON.

   • When you first enable at the workspace level, repo settings default to OFF, so you must enable it per repo.

   • If the workspace setting is turned OFF, repo settings revert to OFF and can’t be changed until workspace is re-enabled 1.

Wait for Activation

• There is a short delay (about 15–30 minutes) after enabling before Code Reviewer starts running on new pull requests.

Also, here's a few public links our team had put together!

Activate Code Reviewer
Activate Deployment Summarizer

Activate Pipeline Troubleshooter

Please let me know if this was helpful or/and if you need more help! 

Kindest regards,

Jovana