Dr Valeri Colon (Connect Centric) Community Champion

Welcome to the community @Maxime Doucet A 400 during the Slack→Rovo onboarding usually isn’t an Org Admin issue. It happens when the Slack workspace hasn’t granted the required permissions, when the site isn’t fully enabled for Rovo in Slack, or when rollout flags aren’t active for your tenant. Being Atlassian Org Admin…

Welcome to the community @Johannes Modersohn Rovo MCP should still work for general Jira/Confluence access, but some MCP features now depend on having Rovo Dev licensed because the same backend powers both. If your org lost Rovo Dev credits or licensing, MCP calls that require dev-level actions can fail even though basic…

Welcome to the community @Mora Carpentier This isn’t a configuration issue — Opus 4.6 is currently experiencing backend failures. The model started returning “Failed to generate an LLM response” around Feb 5 and has been intermittently unavailable since. Other models work because only Opus 4.6 is affected. Atlassian is…

Hi @Cynthia Lane and @Mora Carpentier Others are seeing this too. The Opus 4.6 model is having intermittent backend failures, which surface as “Failed to generate an LLM response.” It’s not a config issue on your side. Atlassian is routing traffic away from the model while it stabilizes, so use another model until it’s…

Welcome to the community @Mike Stone This happens because the Edit button uses JPD’s edit-idea permission model, even though the idea isn’t created yet. Rovo still checks whether the user has a JPD license before letting them edit the draft card. Unlicensed users can view the preview but can’t modify it. There’s no…

Hi @Philip Rovo’s website connector is much stricter than other AI indexers. It requires the site to be fully reachable by Atlassian’s crawler, allowlisting atlassian-bot in robots.txt or headers, and permit cross-domain fetching. Many public sites pass human access but fail crawler checks or block required resources…

I'll add to this @Alexandra Lambert with: Atlassian hasn’t published final pricing or credit-consumption tables yet. Rovo Dev credits, post–March 1, will follow the same model shown in your Admin → Billing → Atlassian Intelligence page, where your site’s credit rate and forecast will appear once billing is enabled. A…

Welcome to the community @Ramesh Muthusamy I'll add to the suggestion by saying: Rovo doesn’t expose a confidence score or reliability metadata for agent responses, so you can’t automate “only post externally if confidence > X.” The agent output is text-only, and Automation receives no confidence field to evaluate. Current…

Hi @KC Wong Rovo often uses relative date syntax like created >= -12M, which isn’t valid JQL. Jira requires functions such as startOfMonth("-12") or created >= -52w. This isn’t a configuration issue—Rovo doesn’t always generate correct date math for months or years. The workaround is to correct the JQL manually or instruct…

Welcome to the community @Mohamed Anwar Rovo can expand coverage, but it doesn’t guarantee a fixed number of test cases because it can’t track test counts across turns. Linking test cases to a story with “is tested by” also fails unless Jira fields and link types are explicitly mapped in the action. Add clear instructions…

@lila Rovo can’t reliably fetch full changelogs, paginate large JQL results, or read complete Development panel data, so your agent’s instructions depend on capabilities Rovo doesn’t have. It only sees partial issue data and may return different results each run. To make this work, use an external layer (Automation, Forge,…

@KC Wong That’s expected today. Customers on the JSM portal don’t get access to your custom Rovo agents or agent skills. They only see the lightweight Rovo experience that can search the knowledge base and draft answers. Only licensed users (Jira/Confluence users) can run full agents, including skills like creating work…

Welcome to the community @Sukrit Phaopanich Rovo MCP’s domain allowlist currently accepts only standard web domains that match Atlassian’s verified-domain pattern, and some newer TLDs (including .ai) are rejected even if they’re valid DNS domains. This is a limitation of the MCP domain-validation rule, not your setup.…

Welcome to the community @James Hainaut Rovo Dev in VS Code currently supports Atlassian Cloud sites only, and those always use the .atlassian.net domain. Sites on .jira.com are not supported by the Rovo plugin, and there’s no override or manual domain entry available. Atlassian hasn’t announced support for…

Welcome to the community @Tejas N This usually happens when RovoDev can’t open an interactive session—most often due to a missing or blocked MCP connection, or the shell not being able to stay attached. Quick checks: • Make sure you run it from a directory you have write access to.• Try launching it directly from a…

Welcome to the community @Jitesh Revankar A constant “network error” usually isn’t caused by your agent or browser. It typically means Rovo is hitting a temporary backend outage, slow response, or timeout on your site. If every request fails, try a fresh browser session. If it continues, capture the timestamp and open a…

Hi @David Foote Rovo’s Create Request skill on the JSM portal is still limited. It often copies only the summary because the portal flow doesn’t reliably pass the full conversation text into the Description field. This isn’t a configuration issue on your side—it's a current product limitation. The best workaround is to add…

Welcome to the community @Edward Jack Right now Slack always talks to base Rovo, not a specific agent, unless you explicitly open that agent’s chat. There’s no way to set a default agent, add routing rules, or attach scenario-level system prompts for Slack messages. Custom agents only run when the user selects them. If you…

To quote @Trudy P Claspill As this is a user community where users help users, it is not the best path to get a feature request to Atlassian. As a Product Admin you should have access to open a Technical Support ticket to ask Atlassian to open the change request or let you know the link if one already exists. Alternately…

Welcome to the community @Aaron Liang That error usually happens because Cursor’s MCP client still expects the /v1/sse endpoint, not /v1/mcp. Atlassian’s remote MCP server won’t complete the auth flow through /v1/mcp, which leads to the “something went wrong” message after approval. Try: npx -y mcp-remote <a…

Welcome to the community @Nick Koukounakis You’re correct: Atlassian’s remote MCP server does not yet implement the OAuth 2.0 Protected Resource Metadata endpoints required by RFC 9728, and it does not expose resource_metadata in the WWW-Authenticate header. Only the authorization-server metadata endpoint is live. This…

Hi @Alessio Franceschelli welcome to the community. At the moment, GitHub Copilot CLI doesn’t support authenticating to Atlassian MCP, so you can’t use Rovo tools or background agents through the CLI. MCP requires its own OAuth 2.1 flow, which Copilot CLI doesn’t implement yet. Atlassian has acknowledged interest in…

Welcome to the community @Rhick Esteves and @Ryan Boyd is correct - Rovo’s Google Drive connector doesn’t yet allow selecting individual files or folders. Once connected, it indexes Drive at the scope granted to the app, and you can’t narrow it to a specific path for an agent. This is a current limitation of the connector…

Welcome to the community @Ryan Mboya Opus hasn’t been removed, but some sites may not see it due to region, rollout phase, or temporary service limits. Model availability can differ across Atlassian sites in the same org, and glitches are usually tied to backend load or a partial rollout. If Opus disappears or fails to…

In order words @matej Rovo Dev’s Bitbucket code review does not currently read or use CLAUDE.md or other repo-level AI config files. It reviews diffs, file context, and surrounding code, but it doesn’t ingest custom model instructions from the repository. If you want Rovo to follow specific guidelines, you need to include…

I'll add to @Nikola Perisic says with Atlassian has open requests for more control, so this may change in a future update.

Hi @liu924645150_qq_com welcome to the community. RovoDev uses a multi-line prompt mode where regular Enter sends the request, so you must use \ + Enter to create a new line. There’s no setting to change this yet, and the behavior is the same across terminals. The only workaround is exactly what you’re doing—custom…

@Patrick Sittinger . Atlassian has stated that Atlassian-hosted LLMs with regional processing (including EU options) are planned, but no rollout date or configuration controls are available today.

virtual hugs @Andrew Boeger Rovo can replace Assist, but it doesn’t yet act as a drop-in “monitor Slack and deflect tickets” bot. Assist still owns the Slack/MS Teams handoff layer. What Rovo can do today is improve summaries, triage, and follow-up questions after a request is created. For true Slack deflection, you’d need…

Hi @Georg Fankhauser There’s no published ETA for a fix, and agent behavior won’t improve until backend support for attachment ingestion is updated. Atlassian recommends watching the ticket for status changes; inactive assignees don’t block progress, as work is handled by the product team rather than the named individual.