Skip to content

Conversation

@teg-atlassian
Copy link
Contributor

@teg-atlassian teg-atlassian commented Jan 28, 2026

What Is This Change?

Users that want to use Rovo Dev sometimes get an error which is caused by their site not having Rovo Dev as an app or they, themselves, not having permission

Anyways, the error message in such cases generic errors such as "Failed to Start Rovo Dev" followed by a stack trace that is unhelpful.

In this PR,

  1. We give a more graceful experience for the user
  2. We nudge the user to register for Rovo Dev

How Has This Been Tested?

Screenshot 2026-01-28 at 7 19 41 PM

The URL link opens as expected when clicked

Basic checks:

  • npm run lint
  • npm run test

Advanced checks:

  • If Atlassian employee & Bitbucket changes: did you test with DC in mind? See Instructions

Recommendations:

  • Update the CHANGELOG if making a user facing change

You don't have access to Rovo Dev Standard
Ask your organization admin to add you to Rovo Dev Standard.
More about code review errors

@teg-atlassian teg-atlassian changed the title handling when user doesn't have access to rovo dev app AXON-1832-Graceful-Handling-Of-No-Sites-Found-Error Jan 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants