Rovo Dev designed to integrate with other Git servers

[Valentina Mannara]

Hi all, is Rovo Dev designed to integrate with Git servers other than Bitbucket Cloud?

If so, which ones, and with access to the teamwork graph information if you have Jira and Confluence Cloud?

Thanks

[Jovana Dunisijevic]

Hey @Valentina Mannara 

Rovo Dev is not limited to Bitbucket Cloud only!

Today we explicitly support:

• Bitbucket Cloud

• GitHub

These are the two providers where we currently have native, productionzed integrations (e.g., PR review, branch/PR operations, repo indexing).

Teamwork Graph context:

Access to Atlassian context (Jira, Confluence, etc.) comes from the Atlassian Teamwork Graph, not from the Git provider itself. That means:

• If you have Jira and Confluence Cloud connected to Rovo / Rovo Dev,

• And your users have permission to see that Jira/Confluence content,

…then Rovo Dev can bring that context into your development workflow regardless of whether your code is in Bitbucket Cloud or GitHub.

So the pattern is:

• Git provider = where Rovo Dev reads/writes code (Bitbucket Cloud, GitHub today).

• Teamwork Graph (Jira/Confluence Cloud) = where Rovo Dev gets rich organizational context (issues, docs, runbooks, designs, etc.).

I hope this helps!

Jov

[Valentina Mannara]

Ok thanks @Jovana Dunisijevic  so Rovo Dev could access to the teamwork graph context on both GitHub and Bitbucket? Are there any other rovo dev integrations on the roadmap, even just Bitbucket DC?

Thanks

[Jovana Dunisijevic]

Hey @Valentina Mannara 

Yes – Rovo Dev is powered by Atlassian’s Teamwork Graph, so it can use organizational context across your Atlassian tools (Jira, Confluence, Bitbucket, Compass, etc.) regardless of whether your code is in GitHub or Bitbucket.

• For GitHub, Rovo Dev connects via an app/integration so it can understand your repositories, branches, and pull requests, and tie them back to Jira issues and other work tracked in Atlassian.

• For Bitbucket Cloud, it has a native connection, so activity in Bitbucket is already part of the Teamwork Graph.

If you have a hybrid setup (some repos in GitHub, some in Bitbucket Cloud), Rovo Dev can work across both as long as both integrations are connected to the same Atlassian tenant.

Today, our focus is on deep integrations with Atlassian Cloud products and GitHub, however for Bitbucket DC Rovo connector is under active discussion, but it’s not something we’ve publicly committed to or announced a timeline for yet.