Dr Valeri Colon (Connect Centric) Community Champion

@justinandradeqkb9609 @Johannes Fliß @Eileen This is a known hiccup with the recent 0.11.24 update—Rovo Dev Agents sometimes fail the entitlement check and briefly report that they're not installed, even when they are. A refresh usually fixes it because the backend eventually resolves the entitlement call correctly.…

@Hajime Sato If the Google Drive connector shows Client ID: undefined, that’s expected on Standard plans because the Google Drive connector is only available on Premium and Enterprise. The Client ID appears automatically once the feature is available, so on Standard you won’t be able to enable or test the connector…

@Bhargav Rovo Dev CLI doesn’t surface Compass component data yet. The CLI currently focuses on code actions, Jira context, and Confluence content through the MCP server, but Compass APIs aren’t wired in. The only workaround is calling the Compass REST API yourself from a script or custom MCP. Atlassian has hinted Compass…

@Anant Patel - Network Right now Rovo Agents can only fill fields that are exposed as editable through Jira’s public APIs. Most teams have “Acceptance Criteria” implemented as a custom field, and those custom fields aren’t fully supported in Rovo’s create/edit actions yet—so everything lands in Description. The workaround…

@Eugene Myasyshchev This one’s on Atlassian, not you. They recently tightened the OAuth allowlist for the MCP server, and Cursor’s custom redirect URI isn’t currently included—so the flow fails even if it worked last week. There’s no client-side fix yet. The workaround is to use mcp-remote or wait for Atlassian to re-allow…

@Juan Mackie Rovo Dev CLI hasn’t added Claude 4.5 Sonnet yet—the model list usually updates a bit after Anthropic’s public release, so it should appear once Atlassian finishes compatibility checks. As for GPT-5, Rovo doesn’t use it.

@Shubham Jain You can’t unlink issues through the Atlassian MCP server yet. The Jira tool accepts an update.issuelinks payload, but unlink operations are ignored in the current MCP beta. There’s no workaround—link edits and removals aren’t supported until Atlassian expands the MCP Jira actions.

@Merijn van Hekken Totally understandable confusion. Thank you for providing Atlassian feedback on this. The announcement was for Rovo’s general availability, but Rovo Dev and some advanced features are still in limited beta with a capped number of seats. That’s why access is blocked even though the email went wide.…

@Matt Little @Liam Hall Right now the Atlassian MCP server only supports the legacy SSE endpoint. It doesn’t implement the newer HTTP Streaming protocol from the MCP spec, and Atlassian hasn’t published a timeline for adding it. VS Code works because it falls back to SSE; clients that require HTTP Streaming won’t connect…

@Dor Blayzer Setting labels during ticket creation isn’t fully supported yet. Rovo can reliably populate title, description, and assignee, but custom fields like Labels often get written into the description instead of the actual field. The only workaround is adding explicit field-update instructions or using Jira…

@Juan Mackie Rovo Dev CLI uses Segment analytics to track tool-permission decisions, feature usage, and CLI events. You’ll see them if the CLI is installed anywhere on your system or if another app runs it in the background. Nothing harmful, just telemetry. You can disable logging by turning off analytics in the Rovo Dev…

@Patrick S_ Stuckenberger Rovo can’t index emails added through the Outlook Jira Connector yet, even though they show up in the issue. Atlassian confirmed this and is tracking it under JRACLOUD-96266. For now, teams copy key email text into a field Rovo can read, link a Confluence page with the email content, or upload the…

@DG Hub This is a backend issue, not your setup. The 500 errors mean the CLI can’t reach Atlassian’s Rovo Dev entitlement API, so it thinks Rovo Dev isn’t enabled even when it is. This started after the latest rollout and many users are seeing the same “not enabled” message. The only fix is on Atlassian’s side. Your org…

Hey @noreen_magsumbol — I know from our accelerator that you got this working! For anyone following along, this behavior is expected for now. Rovo’s Slack app still can’t tap into your full Confluence knowledge base the way it can inside Jira, Confluence, or the Chrome extension. Even with the right bot permissions,…

@Fabian E_ @Liam Hall @Pavel Shmelev You can’t. The Atlassian MCP server only issues short-lived OAuth tokens in the current preview, and external clients like Claude Code can’t refresh them automatically. After a few minutes the token expires, leading to 401s. Atlassian hasn’t released long-lived or refreshable tokens…

@Julien No—GitHub’s coding agent can’t use the Atlassian MCP server. Atlassian hasn’t opened MCP to external LLM clients yet, so only approved tools (Rovo Dev, Cursor preview, etc.) can authenticate. GitHub agents can’t provide the required MCP token, so integration isn’t possible today.

@Raghuveer Madhu Rovo doesn’t have a fixed “accuracy rate”—it depends entirely on the data you give it and how well the agent instructions constrain the output. For report generation, Rovo is capped by result-size limits in Search and Jira queries, so it won’t return very large datasets. There’s no config to lift that…

@季鹏 This error is common right now, especially for users in mainland China. The site-creation service relies on Atlassian domains that are blocked or unstable there, so the request fails even when the site name is valid. The workaround is to create the site from a stable VPN or a network outside China. If it still fails,…

@R_ P_ Correct—through the Atlassian MCP server you can’t create or edit Jira issue links yet. The update.issuelinks payload is accepted but silently ignored, and there’s no dedicated createIssueLink tool. It’s a current beta limitation. If linking is important for your workflow, add your vote—this feature is already on…

@Simon Kolivand That error isn’t from Jira—it’s a Copilot Studio limit. The Atlassian MCP server returns full Jira payloads, and Copilot drops anything over its response-size cap, which triggers AsyncResponsePayloadTooLarge. There’s no fix yet. The only workaround is narrowing the MCP call (smaller JQL, specific fields,…

@Lindsay Anthony Yes—this is a known issue. When you add an agent to a team, the UI shows a success message but doesn’t actually save the team because team-level visibility isn’t fully rolled out. Only org admins can enable team sharing, and even then it may not stick after refresh. The current workaround is to keep the…

@Varun Jain We’ve seen Scrum teams get quick wins with agents that prep sprint reviews, summarize blockers across stories, draft retro notes, and turn standup updates into Jira comments. Another helpful one is a “Backlog Hygiene” agent that flags duplicates, missing acceptance criteria, or stories that don’t meet DoR.

@ms c Those logs mean the built-in MCP server can’t start, so the CLI falls back to defaults and becomes unusable. It’s almost always caused by running Rovo Dev inside a container or VM where required binaries, glibc versions, or permissions don’t match what the CLI expects. The only stable workaround today is to run Rovo…

@Inna S Even with Atlassian Intelligence enabled, the Atlassian Remote MCP server isn’t generally available yet. Only a small set of approved customers can use it, which is why VS Code doesn’t show the extension, no auth popup appears, and no MCP settings show in admin. For everyone else, connections stay stuck on…

@jack User thumbs-down feedback isn’t exposed anywhere in the UI yet. Rovo logs it internally for Atlassian, but orgs can’t view or export it, and it can’t auto-create Jira issues. If you need actionable feedback, the workaround is adding a “Report an issue” macro or form on key pages until Atlassian makes Rovo feedback…

@Sun Todd This error happens when Atlassian’s identity service can’t complete the Google-OAuth handshake. It’s usually caused by regional network blocks (common in mainland China) or a temporary outage on Atlassian’s side. Try again using a stable VPN or a non-Google login. If it still fails, send the Anonymous ID to…

@Alessandro Paiardini That message appears when the Rovo Dev CLI can’t reach the model service. It’s usually caused by temporary outages, regional routing issues, or the recent backend changes that made model requests unstable on Linux. Nothing in your setup is wrong. Most users on Ubuntu 24 are seeing the same…

@tim roya @Ethan @Eileen This warning means the CLI can’t reach the Jira Cloud API for your site. It usually happens when the latest Rovo Dev update breaks project discovery or when your site temporarily loses the Rovo Dev entitlement. It’s not your config. The fix is on Atlassian’s side and already being worked on. Most…

@Brian Hu You’re running into a known regression in the latest Rovo Dev release. Even when Rovo Dev Agents is enabled, the CLI sometimes can’t read the entitlement and shows “not enabled.” It’s a backend issue on Atlassian’s side, not your config. The current workaround is to have your org admin toggle Rovo Dev off/on…

@varghese-jose This happens when your site’s Rovo Dev entitlement was removed or expired, which makes the CLI think Rovo isn’t installed. Atlassian recently updated access rules, and some sites lost preview access. Your org admin must request Rovo Dev to be re-enabled for that site through Atlassian Support. Once it’s…