Dr Valeri Colon (Connect Centric) Community Champion

@Sven Meyer I love the "more bugs and annoyances here" Totally hear the frustration. The freeze/unstoppable-run bug is a known issue in the current Rovo Dev CLI. Ctrl-C and Deny don’t reliably stop the session, and several standard dev-tool commands (like --version) aren’t implemented yet. The workaround is to restart the…

@Sean Wood Rovo times out because the prompt is far beyond what the agent model can reliably parse. Very long, multi-step “interactive workflow” prompts exceed the token and reasoning limits for Rovo Agents. The only stable fix is to break this into smaller agents or move the logic into a Rovo Dev agent where you can…

@Leonardo Zhou That error isn’t about the name—it's a backend failure in Atlassian’s site-creation service. It happens when your org isn’t allowed to create new sites or when the Dev Agents preview isn’t fully enabled. Ask your org admin to confirm site-creation permissions. If that’s already on, share the Anonymous ID…

<a href="https://community.atlassian.com/forums/user/viewprofilepage/user-id/5941654">@Naga Raj</a> acli rovodev auth login doesn’t accept a token file. It only reads a token piped via stdin or entered interactively. Use: type token.txt | acli rovodev auth loginAlso be sure the token is an Atlassian API token from your…

@Mirko Grahnert @Sing Chen Rovo Agents can read Atlas goals but can’t reliably filter by custom fields or pull goal updates yet—the Atlas API exposure inside Rovo is limited. Most agents fall back to keyword search, which causes inconsistent results. The only stable workaround today is passing the goal URLs or IDs directly…

@Natalie Beaulieu This is awesome news! The Jira Data Center connector fills a huge gap for hybrid orgs. My top request: expand indexing to include full issue history and work logs, not just fields. And a Bitbucket Data Center connector would be a huge win for teams still running on-prem SCM.

@yogesh kn Atlassian hasn’t published Python examples yet. MCP access is still limited, and the only supported clients are the ones Atlassian ships (e.g., Rovo Dev). You can use the open-source MCP spec to build your own Python client, but Atlassian’s MCP server won’t authenticate external LLMs like Gemini/OpenAI yet. No…

@FERMENICH, JUSTIN D. Rovo is prompting because the agent isn’t allowed to write directly. If an action requires “confirmation,” it means the agent isn’t fully trusted for that operation. To fix it, enable Trusted Actions for the agent in Studio and make sure the automation actor has “Edit issues” + “Manage sprints / Add…

@Sandesh S Bhalerao The Atlassian MCP server isn’t open for third-party clients like Gemini yet. It requires an Atlassian-issued MCP token and a supported client handshake. Gemini CLI can’t authenticate or maintain the SSE connection, which causes the disconnect/404 errors. There’s no public integration path right now, so…

@Peter Cary Rovo processes data in the same region as your Atlassian Cloud products. If your Jira/Confluence data residency is set to US, EU, AU, DE, JP, etc., Rovo runs its processing in that same region. Customer data isn’t used to train Atlassian’s models, and it doesn’t leave the residency region for processing. @Sabin…

@a b That message is a generic Atlassian platform error. It usually means the request hit a backend failure—often site-creation, permission checks, or a service outage. @Nikola Perisic mentioned try again once, then as share the Anonymous ID with Atlassian support. They can trace exactly which service failed and why.

@[deleted] MCP servers don’t handle Atlassian auth directly. If your client runs in a container, you must pass an MCP-signed token or API key into the container and let the client authenticate to the server. Environment variables work best. The server won’t generate or refresh tokens for you, so the client must handle auth…

That's fantastic to hear. @Rebekka Heilmann _viadee_ and I have an event on Monday so I'm auditing the forum to close loops. I happily take "a lot of progress".

@Gabriel Rojas Rovo can generate the summary, but it can’t auto-post it on a schedule alone. The reliable setup is: Jira Automation runs weekly → sends the Initiative + its children to a Rovo Agent → the agent produces the status summary → Automation writes the comment back. Rovo Chat can’t do this; only Agents paired with…

@theo-henrik.hollweg Rovo Chat doesn’t read the page tree today. It sees each page as an indexed document, not its position in the hierarchy, so it can’t place new pages relative to your current location or prioritize nearby subpages. Page-tree awareness is a top feature request, so adding your vote helps push it forward.

@Kishan Gupta That endpoint doesn’t accept OAuth tokens from your Atlassian account. The MCP server requires a signed MCP-specific token generated by an approved client, not the standard access/refresh token pair. Even valid Atlassian tokens will fail with “invalid_token.” There isn’t public access yet, so the connection…

@Jessica Wernham Rovo doesn’t index Questions for Confluence today. It only ingests native Confluence pages and supported apps; Questions stores content in its own data model, so it’s invisible to Search and Chat. There’s no workaround yet. If you want it indexed, add a feature request—this one is already gaining traction.

@Christian Mullane Rovo can update Confluence pages, but only through a Rovo Agent with the 'Update Confluence Page' action enabled. Rovo Chat itself can’t write changes back. Create an agent, give it access to the space, add the update action, and run it on each page. Also confirm you have edit permissions—without that,…

@Colton_Kosicek Rovo agents can run inside automations, but they don’t inherit full issue access. Automations pass only the fields in the payload, and child issues often aren’t included. If the agent tries to re-fetch the story, it fails unless the automation user has browse + view permissions for that project. Add those…

@Mahanth Prudhvi P The Gmail connector indexes mail per user, not for the whole org. Each person must connect their own Gmail, and Rovo can only search the messages for the user who granted access. It doesn’t scan company-wide inboxes or other employees’ mail. If you search, you only see results from your Gmail account.

@Brian Cason This is a common issue. Thanks for providing Atlassian with the feedback. It happens because the agent isn’t using the JQL result set to build the table—it’s re-querying or summarizing from memory, which causes drift. To fix it, force the agent to: store the JQL results, iterate over that stored list only, and…

@Mahanth Prudhvi P I think @Nikola Perisic is right on. The Gmail connector indexes only the Gmail accounts that users individually connect. It doesn’t give Jira or Rovo access to everyone’s mail. If you connect your Gmail, search results include your messages; if a coworker connects theirs, they see their messages.…

@dschaendlinger That error usually means the API token doesn’t match the site you’re logging into or Rovo Dev isn’t enabled for your org account. Make sure you’re using your actual Atlassian login email (not @atlassian.com) and the API token from the same site shown in the login URL. If it still fails, your org admin needs…

@Karri Adkins This usually happens when the project’s required-field config doesn’t match what Rovo sees. Even if Assignee isn’t required for humans, Jira may still mark it as required via workflows, field contexts, or issue type schemes—causing silent failures. Check the project’s field configuration, workflow validators,…

@Allan Work Space That means acli.exe isn’t on your system PATH. When you run it from C:\Users\user, Windows finds the local copy, but any other folder can’t. Add the folder containing acli.exe to your PATH environment variable, restart your terminal, and the command will work globally.

@Colton_Kosicek Rovo Actions can fire multiple steps, but they’re still limited in how reliably they chain updates. In complex flows, agents often overwrite fields or lose context. The most dependable approach today is splitting the workflow across smaller agents or using one agent with very strict, step-by-step…

@Rick H @S That loop happens when the site-level Dev CLI flag is out of sync. Even if it shows “enabled,” the backend sometimes drops the entitlement. Have your org admin toggle Rovo Dev CLI off/on from Admin → Rovo Dev Agents, then recreate the API key. If the message persists, open a support ticket—the issue is on…

@Colton_Kosicek Rovo can create multiple stories, but linking them back to the parent is fragile. The agent must output each issue key and call the update-issue action with parent set explicitly. If required fields or issue types changed, the link step silently fails. Check the project’s hierarchy settings and run logs in…

@KawaCheng That’s a known limitation. The CLI expects UTF-8, and an .agent.md saved as ASCII with CJK characters will crash on start. Re-save the file as UTF-8 without BOM and the CLI will load normally. If it still fails, reinstalling the extension forces a clean parse, but the root fix is the file encoding.

@John Mahony To use a Rovo agent in JSM, it must be published with JSM channel access. In Studio, open the agent → Visibility → enable Jira Service Management. Your org admin also needs to allow Rovo for JSM in product settings. Once both are on, the agent appears in the AI menu in requests.