Dr Valeri Colon (Connect Centric) Community Champion

@Mike Marino Rovo can’t reliably run JQL functions provided by apps like Xray. It only supports Jira’s native JQL functions, so calls like testPlanTests() often return empty sets even if they work in Jira. There’s no fix yet—the agent must use standard fields instead of app-specific JQL. If you need Xray JQL support, it…

@Leung Joe This error comes from a known bug in the Linux build of Rovo Dev CLI where the bundled HTTPX client crashes during cleanup. It doesn’t mean your setup is wrong. The workaround is to run acli rovodev run inside WSL or a container, or downgrade to a previous CLI build if available. Atlassian is already tracking…

@Pragnya Prasu Sahoo Rovo can only set fields that the create-issue action exposes, and today that’s basically title, description, assignee, and a few basics. Story Points, Sprint, and Labels aren’t writeable from Rovo yet, even if you include them in the prompt. There’s no published ETA. The workaround is: create the…

@Yong Zhu Lai Rovo Agents can’t call external APIs directly. When you’re building with Forge, the agent runs inside a restricted runtime—only Forge Remote or Forge’s built-in fetch with declared permissions can make outbound requests. Local code works because it has open network access; Rovo doesn’t. To call GCP or any…

@April Wang Right now you can’t register your own OAuth client for the Atlassian Remote MCP server. Only Atlassian-approved MCP clients are allowed, and the MCP auth server won’t issue tokens to 3LO apps. No public client registration, no confidential-client flow, and no dynamic registration. Redirects are limited to…

@omer ugur Thanks for sharing this—your analysis is correct. MCP tools can fail on Linux when Rovo Dev’s bundled libstdc++.so.6 is built against a newer GLIBC than the system provides. Renaming the bundled library forces Node to use the system version, which fixes the mismatch. This workaround is safe and the most reliable…

@Srinath Chandrasekaran The Atlassian Remote MCP server isn’t fully supported in Cursor yet. Its OAuth flow uses a PKCE pattern Cursor can’t complete, which causes the Invalid PKCE code_verifier error. With mcp-remote, the token isn’t durable because Atlassian hasn’t opened long-lived tokens for external MCP clients—so…

@Christian Walther Rovo can’t reliably detect or read a page’s parent today, as @Rebekka Heilmann _viadee_ points out. It indexes each page individually and doesn’t fully use the Confluence content tree, so parent lookups often return random pages or nothing—especially after moves or when folders are involved. The only…

@liuyang zhang This issue is common for users in mainland China. Several Atlassian domains needed to create a Rovo Dev site are blocked or unstable there, so the request fails even when the site name is fine. The workaround is to use a stable VPN or create the site from a network outside China. Once the site is created,…

@Rob Stevenson There’s no full public reference for ~/.rovodev/config.yml yet. Only a few settings—like tool permissions, allowed paths, and workspace limits—are documented in the Rovo Dev support pages. Atlassian hasn’t published a complete schema, and many fields are still experimental. For now, the support docs +…

@Dan Rovo Dev runs tools inside its own sandbox, not your full PowerShell environment. It doesn’t inherit your PATH, env vars, or shell features, so commands like dotnet, bash, or custom env vars won’t resolve. Today the only workaround is adding those paths manually in allowed_external_paths or running Rovo Dev inside…

@Paul Swartout Rovo doesn’t index JSM Operations yet, so on-call schedules aren’t available to Search or Agents. Only Jira, Confluence, and supported connectors are exposed. Atlassian has confirmed Operations data is on the roadmap, but not released or in beta. If you want early access, add your vote to the feature request…

@Amogh Agrawal This failure isn’t your config—it’s caused by the corporate proxy blocking Rovo Dev’s outbound domains, which triggers the SQLite/MCP-server crash you see in the logs. The fix is to whitelist the Rovo Dev endpoints. Teams using Netskope resolved it by allowing:…

@lingchuangmengs Win11 上出现 “✗ Error: failed to execute the command” 多半是因为 acli.exe 不在当前目录，也没有加入 PATH。只有在安装目录运行才会成功。请找到 acli.exe 的实际位置，把该文件夹加入系统 PATH，然后重开终端再运行 acli rovodev run。如果仍然失败，确认 Rovo Dev 已在你的站点启用。

@Dorin_Goldin @Don Ayers @Jaakko Pakarinen @Cristina Maria Rodrigues Garcia Araújo @Ivan Đorđević This isn’t a VS Code issue—the Atlassian Remote MCP server is still in limited preview and only supports the legacy SSE protocol, which frequently returns 404 or never completes the initialize handshake. Non-approved clients…

@Steven Pham The 60-second tool timeout is hard-coded in the current Rovo Dev CLI, and you can’t override it. Long-running MCP tools will always be cut off and the LLM will continue without the results. The only workaround is making the MCP return partial/streamed output quickly or splitting the analysis into shorter…

@Damyan Doykov The Atlassian Remote MCP server isn’t open to external clients yet. Only Atlassian-approved clients can authenticate and use tools. Non-approved apps can connect to the SSE endpoint but can’t interact. There’s no public onboarding or auth doc right now—you can’t become an approved client until Atlassian…

@Heather Curcio Rovo Agents are only available to users inside your org, never outside your company. Visibility is controlled at the agent level, not just Confluence permissions. You choose whether the agent is private, shared with specific teams, or available org-wide. Even if a user has Confluence access, they won’t see…

@hans peter Piped commands aren’t supported in toolPermissions today. The CLI matches single-command regexes only, so patterns like find.* | head.* won’t work. Each command in the pipeline has to be permitted separately. If you need pipeline-level rules, that’s a feature request—Rovo Dev doesn’t parse or allow…

@ricardokullock Rovo Dev CLI doesn’t let you hide or disable its built-in tools. Even if you deny them, the LLM still “sees” those tools and will try them first. Only MCP tools can be added—not replace defaults. The config isn’t public yet; the only docs are in the Rovo Dev CLI support pages. A feature request to allow…

@lucaminudel Great suggestion. The CLI doesn’t support audible BEL cues today—permissions prompts are silent unless the terminal itself beeps on stdin waits. Adding an optional, distinctive sound for Rovo prompts would need to be built into the CLI. Definitely worth submitting as a feature request so the team can consider…

@u633401 Rovo can create Xray Tests, but it can’t set the testType to “Cucumber” because the Xray-specific fields aren’t exposed in Rovo’s create-issue action. It defaults to “Manual” no matter what you put in the prompt. There’s no workaround today—the Xray custom fields must be set after creation. Atlassian needs to…

@Marvin Meyer-Kahlen There’s no public roadmap for the Atlassian Remote MCP server yet. The only official list of limits is the Known Limitations section in the support doc—you won’t find a longer list in the Community. Atlassian is still in early access and updates the doc as features land, so that page is the single…

@mia samiiya You don’t need a new API token. Windows just can’t find acli.exe anymore. The first run worked because you were in the folder that contains the file. After reboot, your terminal isn’t in that folder and it’s not on your PATH. Add the install folder (where acli.exe lives) to your PATH, restart the terminal, and…

@amit.deb Automation can’t apply the raw JSON you generate. Rovo Agents must output only the field values, not a Jira REST-style update object. The automation action builds the JSON for you. Have the agent return a simple object like: {priority:"High", impacted_team:"X", …}. Then map each value in Edit work item fields. If…

@Wang Paul This is a known Windows-only issue. Rovo Dev CLI can’t run Python blocks in Win11 CMD/PowerShell because of how Windows handles stdin/stdout for interactive code. It works in WSL, Git Bash, or inside a container. Until Atlassian ships a fix for native Windows execution, the workaround is to run the CLI in WSL or…

@Jonah Jacobsen Rovo Dev CLI is currently compiled against glibc 2.35, so it won’t run on CentOS 9’s 2.34. Atlassian hasn’t released a 2.34-compatible build yet, but this request is on their backlog. The only workaround today is running the CLI inside a container or VM with glibc 2.35+. Adding your request helps push for…

@mia samiiya The meters work like this: Session context resets every time you restart the CLI. Daily total resets every 24 hours UTC. Hitting the daily cap pauses Rovo Dev until the next reset, but you can still start a new session tomorrow and reuse your prompt—Rovo doesn’t block that. The limits don’t “stack”; they…

@anthony_ng If a custom field is on the screen but not visible in a work item, it’s almost always a context issue. Check the field’s context (issue types + project scope). If the context doesn’t include this project and this issue type, Jira hides the field even if it’s on the screen. Update the field context, reindex if…

@James Bylett This is a known false positive. Microsoft Defender occasionally flags the atlassian_cli_rovodev.exe binary because of the way it bundles its runtime, not because of actual malware. Atlassian has verified the file is safe. Updating Defender’s definitions or adding the binary to your allow-list resolves it.…