Filter which Pull Requests get a review from RovoDev

[Gustavo Campos]

I would like to filter which pull requests get automatically reviewed by RovoDev, let's say do not automatically review anything that's on a "release/*" branch or which has "master" as destination, we're spending lots of credits on that.

How can I open an issue or request for that feature to be added?

[Jorge Cammarota · Accepted solution]

Good morning today the official way to talk to the Rovo/Rovo Dev team is through Atlassian support. The general flow is:

Access the Rovo/Rovo Dev Support Center
Starting point: https://support.atlassian.com/rovo/

Open a support ticket / product feedback:
In the Support Center, you choose a request type (for example, something like “Question about product” or “Feedback / improvement request” linked to Rovo or Rovo Dev*.
Describe that you want an auto-review filter based on:
name of the source branch (ex.: release/*)
destination branch (ex.: master)

[Dr Valeri Colon _Connect Centric_]

Welcome to the community @Gustavo Campos You’re not alone—others are seeing similar behavior. What’s happening is usually a context difference between Studio and the regular chat, not an actual loss of permissions. In Rovo Studio, agents run with full design-time context and easier access to configured knowledge sources. In the normal chat, they operate strictly under the user’s permissions and current indexing state. If this changed suddenly, it’s likely a temporary backend or indexing issue, so capturing a timestamp and contacting Support is the best next step.