atlassian / atlassian/atlascode

Cannot use Rovo Dev with a *.jira.com site because it is not saved as a cloud site

Open
#1,369 6 comments 0 reactions 1 assignee View on GitHub

@bwieger-atlassian-com is already working on this.

Since Dec 3, 2025.

auth closing-soon Rovo Dev
Dominant language
TypeScript
Stars
130
Forks
82
Avg merge
3h 3m
Merged PRs (30d)
6

Description

Describe the bug
When adding an API Token for a *.jira.com site, the extension saves the site with "isCloud":false. Rovo Dev cannot use it, because ClientManager.getCloudPrimarySite() only considers sites where isCloud === true, so it never returns it as a primary site. As a result, Rovo Dev in VS Code always reports:

RovoDevEntitlementError: No valid Rovo Dev credentials found

To Reproduce
Steps to reproduce the behavior:

  1. From the VS Code activity bar, select Rovo Dev.
  2. Click "Add API Token".
  3. Enter a *.jira.com site as the Base URL.
  4. Enter your email.
  5. Enter an API token.
  6. Click "Save Site".

Expected behavior
Rovo Dev view should show "Welcome to Rovo Dev Beta"

Observed behavior

  • Rovo Dev view keeps showing the "Add API Token" button.
  • Output log contains "Unable to check Rovo Dev entitlement RovoDevEntitlementError: No valid Rovo Dev credentials found"
  • globalStorage shows the site saved with "isCloud":false

Environment and Version:

  • Atlassian Plugin Version 4.1.62 and 4.0.11
  • Visual Studio Code Version 1.106.3
  • OS: Windows, Linux (WSL2)

Additional context
There seem to be places in the code where only URLs ending in '.atlassian.net' are considered to be cloud URLs, and '.jira.com' URLs are not considered. For example here:
https://github.com/atlassian/atlascode/blob/00541b23df4f27f93684f7f3b5fe472b71eeb8c3/src/atlclients/loginManager.ts#L32

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.