Rovo dev configuration issue

[Toni Lahnalampi]

I activated Rovo dev pull request reviews following to these guides:

https://support.atlassian.com/rovo/docs/turn-rovo-dev-features-on-and-off
https://support.atlassian.com/rovo/docs/activate-code-reviews-in-your-repository

Rovo dev activated and I created a test pull request to verify everything works.

The problem is, that only I (admin) am able to trigger rovo dev on pull requests. Other users receive error:
The code review could not be completed because your connected site does not have the Rovo Dev app installed.

Other users are using the same site I am using.
I chatted with atlassian AI bot but it just provided me with the same links I had already configured and verified multiple times.

It seems like a permission issue that is not mentioned in the guides. What could that be?

[Jovana Dunisijevic]

Hey @Toni Lahnalampi 

A couple of important constraints that aren’t very obvious in the docs:

1. Only the pull request author can manually trigger Rovo Dev on a PR
   In Bitbucket, the “Review code / Analyze code” action is limited to the author of that pull request. If another user (even an admin or reviewer) opens the same PR and tries to trigger Rovo Dev, it will fail.
   This is documented here under “Things you should know”:
   Activate code reviews in your repository | Rovo | Atlassian Support

2. The PR author must have Rovo Dev credits on the connected Jira site
   In your Bitbucket workspace settings, you’ve selected a Jira site under Rovo Dev credits.

   • Rovo Dev will deduct usage from the PR author’s credit allocation on that Jira site.

   • If that user doesn’t have Rovo Dev enabled/allocated on that site (or has no remaining credits), the review will fail.

   • As an admin, you’re likely enabled and have credits, which is why it only works for you.

To confirm and fix this:

1. Ask one of the affected users to:

   • Create a new test PR themselves (so they are the author), then

   • Try to trigger Rovo Dev from that PR.

2. If it still fails:

   • Check in Atlassian Administration that Rovo Dev is enabled for your org and site:
     Turn Rovo Dev features on and off | Rovo | Atlassian Support

   • Make sure that user is allowed to use Rovo Dev and has credits on the Jira site you selected under Rovo Dev credits in the Bitbucket workspace settings.

If they’re still getting the same error after confirming both of those, then it’s likely a genuine product issue rather than configuration and we should raise a support ticket with the site + repo + PR details so the Rovo Dev team can investigate the specific failure.

Let me know how you go!

[Toni Lahnalampi]

Thanks for your answer.
1. User that was trying trigger rovo dev review was the author of that pull request.
2. Jira site has credits for that site as far as I know and Rovo dev is activated from Bitbucket workspace.

But at the meantime I think we managed to make Rovo Dev work by setting a role for Rovo dev in admin.atlassian.com App access settings for our domain. 

"Any domain" had Rovo dev role "User".

Our domain had Rovo dev role "None". After changing role to "User", Rovo reviews started to work for all users.