Dr Valeri Colon (Connect Centric) Community Champion

@Rafiqul Islam welcome to the community. This appears to have been a broader Rovo Dev issue, not just your site. Atlassian’s Rovo Dev status history shows an incident on Feb. 13, 2026 where users experienced errors with Rovo Dev not starting, and it was later resolved. If it’s happening again, check the Rovo Dev status…

@Adam Witherington You’re not missing anything—what you’re seeing is accurate. Right now, there’s no reliable way to fully disable the Rovo summary in the issue view, even if AI features are toggled off. The difference you’re seeing between /browse/ and list view is due to different Jira rendering contexts, not a setting.…

@Tautvydas You’re not alone—this usually isn’t on your side. That error during site creation (especially with a Trace ID) points to a backend provisioning issue with Atlassian, often related to billing or tenant setup. Try a different site name, refresh, or use incognito. If it keeps happening, share the Trace ID with…

@Jameszxc_. That error usually isn’t caused by anything on your end—it’s typically a backend issue during site provisioning. The “Agree and start now” button triggers billing and site creation services, and failures like this often come from temporary outages, region or tenant issues, or payment validation glitches. Try…

Welcome to the community @MEENA RITESH Sadly, this one’s pretty common right now—“Agent process terminated (exit code 1)” usually isn’t your code, it’s the Rovo Dev runtime crashing. Try this first: Restart VS Code Run “Rovo Dev: Start new session” Re-authenticate Atlassian account Disable/re-enable the extension If it…

Welcome to the community @Aasif Dar Rovo Dev has had intermittent reliability issues, and errors like this usually point to a temporary backend or connectivity problem, not something wrong with your setup. If you’re seeing Failed to connect to the Rovo Dev API, try: restarting the CLI, re-authenticating and checking your…

@Soojae Kang Short answer: no, not reliably. Rovo doesn’t control how formatting renders in MS Teams. When a Rovo agent sends content to Teams (typically via a connector or action), it’s passed as plain text payload, and Teams only supports limited formatting unless you use Adaptive Cards or specific message schemas. So…

Hi @Sheila Connolly Yes—this is a great use case for Rovo, and people are doing something similar today. Rovo can pull Jira context and generate executive-friendly summaries, but it won’t automatically push to Google Slides. A common pattern is: Use Rovo to summarize Initiatives/Epics → status, risks, progress Then paste…

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.…

Thanks @Josh I went through the channel starting from January this year and scheduled posts for all the juicy threads. They'll come out every Tuesday & Thursday. Can't wait to read what the Champions slack buzzes about after Team26.

@Karoline Rønnow Jensen This behavior is being reported by others as well. What you’re seeing is typically a context difference between Studio and Chat, not a true permission loss. In Rovo Studio, the agent runs with full design-time context and often broader access to test knowledge sources. In the regular chat interface,…

Hi @Ryan lee Rovo Dev in VS Code doesn’t use a separate “dedicated” MCP server—it connects to Atlassian’s same MCP service that’s used for external clients. The difference is that Rovo Dev has native integration and permissions handling, so it can access more context (like Confluence whiteboards) out of the box. Tools like…

This post was sparked by a great conversation with @Darryl Lee in the Champions Slack. He pointed out a Rovo Chat/Agent + JQL quirk and that the AI button next to the JQL search box does pretty good JQL. I filled out the 'why' and 'how' Atlassian could improve the limitation from Darryl's feedback. That question—is this a…

lol thanks @Dave LIAO @ElEscarabajo Rovo likely refused the request because debugging decompiled code and reverse-engineering tools like IDA Pro trigger its safety filters. Even harmless questions can be flagged if they resemble prohibited reverse-engineering assistance. This is a server-side restriction, not a user…

@Rebekka Heilmann _viadee_ and @Tomislav Tobijas that means a lot coming from you both! You’re the ones consistently showing up in the forum and sharing your expertise; without that, my reviews would take F-O-R-E-V-E-R. I’m glad the summaries resonate, Rebekka. I hope they help everyone get a clearer picture of where the…

Yes, this is still the case. Atlassian’s MCP server continues to support only its own authorized clients, and third-party tools like Gemini still can’t complete the required authentication or session flow. Atlassian hasn’t released a public integration method or expanded MCP access, so Gemini → MCP connections remain…

I only know because I too had my work deleted...

Aww thank you for making me feel special @Dave Rosenlund _Trundl_ and thank you for supporting the community @Akash Singh 

Great questions, @Habib ZOUARI For custom Rovo agents built in Forge, knowledge sources aren’t attached in the manifest or via API today. They’re added the same way you configure knowledge for any other agent. Go to admin.atlassian.com → Rovo → Agents → Knowledge and attach the spaces or pages you want. Custom app data…

Hi @Alperen Demirhan Rovo’s Create/Raise Request skill is not customizable. The wording, layout, and confirmation card—including “Review and edit…” and the “Raise request” button—are fixed UI elements. Agents can’t change or remove them, and admins can’t override the text. The only way to alter the flow is to bypass this…

Hi @João Cunha Rovo and the Virtual Service Agent can’t create JSM tickets silently today. Both require an explicit confirmation step—the “Raise Request” card in Rovo and an Intent-triggered action in VSA. These safeguards are part of JSM’s design to avoid unwanted ticket creation. You can’t suppress the card, auto-create…

Welcome to the community @sshalabh I'll add to what Tobi is say, Rovo can’t manage licenses or predict user return likelihood on its own. It has no access to login-frequency data, product-usage logs, or license assignments. If you export that data yourself (via Atlassian Admin APIs), you can feed a processed list into a…

Welcome to the community @edrick.deguzman Rovo can’t reliably enforce per-author, per-issue deduplication because it doesn’t build a structured dataset before reasoning. It sees comments as text, not stable records, so it may re-include older items even with strict instructions. This is a platform limit, not your prompt.…

Welcome to the community @ElEscarabajo Rovo hasn’t gotten “stricter,” but its safety filters have been updated. When a question is unclear or resembles a restricted topic, Rovo may incorrectly flag it as unsafe and refuse to answer, even if the request is harmless. This is a known behavior. Rephrasing the question with…

Hi @Robert Nadon You can request this directly through Atlassian Support or your Atlassian account manager if your org has one. Ask for a Rovo Dev or Bitbucket code-review enablement session—they can route you to the product team or a solutions engineer. If you don’t have an assigned rep, submit a ticket under Bitbucket…

Welcome to the community @Habib ZOUARI Custom Rovo agents don’t get automatic access to all Confluence content. They can only use the knowledge sources you attach and whatever your Forge app passes in, and your app must have the proper scopes to read those spaces or pages. They also can’t access custom app data unless your…

Hi @Lavinia “Failed to load content” after briefly showing an answer is usually a rendering or post-processing error, not an agent or permission issue. It often happens when the response is long, includes tables, or pulls data from multiple sources. Clear browser cache and try an incognito window; switch models; and…

I'll add to this to say: The available Jira actions cover creating and updating issues, but work-log operations aren’t exposed to agents yet. The only options today are logging work manually, using Jira Automation or REST API outside Rovo, or building a Forge/MCP integration that adds work logs and then calling it from an…

Welcome to the community @Vivien RUIZ Custom agents can’t read full Slack thread history. The built-in Rovo Slack bot uses Slack’s native thread context, but custom agents don’t receive that message history even if you enable the “Read messages in Slack” skill. They only get the single triggering message unless you…

Welcome to the community @Vartika Sharma Both MCP endpoints are still unstable and behave like beta services. The SSE endpoint (/v1/sse) can hang after OAuth when the stream never opens cleanly, and the HTTP endpoint (/v1/mcp) often drops sessions with “Session not found.” This isn’t a client issue—it's a backend…