Dr Valeri Colon (Connect Centric) Community Champion

Good question @Georg Fankhauser —there’s now a bit more clarity on this. At the moment, Rovo does not support auth-less MCP servers, even if they are valid and publicly accessible like Microsoft Learn. That’s why you’re seeing the generic error during setup—it’s not your config, it’s a current platform limitation. If you…

@Eric Roetenberg Great question—this is definitely doable today with a mix of Rovo agent design and built-in Jira actions. You’re on the right track with your scenario. Rovo agents can guide users through creating a User Story (asking for summary, description, acceptance criteria, etc.) and then use built-in Jira skills to…

Both @Chris Rogers and @Rebekka Heilmann _viadee_ advice is on the right track. If Rovo apps don’t appear at all, it’s likely a provisioning/eligibility issue—best next step is to contact Atlassian support to enable it for your org.

Great threat ya'll. Yes—this can happen. Rovo agents may switch scenarios mid-conversation if a later reply better matches another trigger; Debug response is the right place to confirm that. To reduce it, make the triggers more mutually exclusive, add stronger negative examples, and tell Scenario B to stay active until…

Welcome to the community @Tsjsjd @Andrew Taro @Bruce C @test this isn’t fixed by switching accounts—Rovo Dev access is controlled at the site level. Even if enabled, users must be explicitly assigned, and new sites can take time to provision. If you’ve added yourself and still see this, it’s likely a rollout/provisioning…

@Rachel Hatcher Initial syncs can vary widely—from under an hour to up to ~24 hours—depending on the connector and data volume, as @Rebekka Heilmann _viadee_ mentions. That said, seeing “0 items” or only 1 object after many hours (especially with a small dataset) isn’t typical. If it’s still stuck, it’s likely a…

To add to this @Jace Anderson what you’re seeing is expected behavior right now—Rovo agents in the JSM portal have limited UI/UX controls, and there isn’t a setting to disable or customize the auto pop-up behavior yet. Several users have raised similar concerns as @Derek Fields _RightStar_ mentions. At this stage, the only…

I'd add to @Tomislav Tobijas comment with there’s no public roadmap confirming an attachFile capability for MCP yet. Atlassian has been actively expanding MCP features, but file attachment support hasn’t been officially announced. For now, workflows typically rely on links or existing integrations. 

<3 @Liz Tanner 

I would add to @Gunjan Kumar comment to say availability still depends on licensing and rollout, so even if enabled, it may not appear everywhere immediately.

@Evgeniy Sabilin welcome to the community. Yes, but don’t solve it by giving people Bitbucket access alone. For Rovo to answer code questions well, Bitbucket content must be available to Rovo on the same Atlassian site, and permissions are respected. In practice, make sure Bitbucket is connected to that Jira/Rovo site, the…

@base There’s currently no supported way to fully disable logging in Rovo Dev CLI. The CLI exposes a log path, but not a toggle to turn logging off. As a workaround, you can redirect or manage logs at the system level (e.g., permissions, cleanup scripts), but native log disablement isn’t available yet. @VB's answer is…

@KPADJA Kokoussè Nestor welcome to the community. Yes — this was a known Rovo Dev CLI bug, not a Linux-only issue. Atlassian confirmed the file-lock problem in v0.13.46 and fixed it in v0.13.47. The best advice is to rerun/update Rovo Dev so it pulls the latest version and try again. If you’re still seeing it, you’re…

@Jovana Dunisijevic and @Truong Tran welcome to the community. This was a known Rovo Dev CLI bug in v0.13.46, not something you could fix by deleting files. Atlassian said the file-lock issue was caused by a new locking mechanism and fixed it in v0.13.47. So the right answer is: update or rerun Rovo Dev so it pulls the…

Hey ya'll for now, treat this as a preview feature—use /hooks help to explore, but don’t rely on it in production yet.

Hey ya'll. This was a known bug in Rovo Dev CLI v0.13.46, not a Linux config issue. Atlassian confirmed the new file-locking mechanism was broken, and the fix was released in v0.13.47. Older versions were not a real workaround because Rovo Dev auto-updated. Best answer: update/rerun so it pulls the latest version and try…

Hey ya'll, Atlassian fixed the config.yml.lock could not be acquired issue in v0.13.47, and users confirmed updating resolved it. The best fix is to rerun/update to the latest Rovo Dev version and try again. Deleting the lock file alone usually did not help. 

@Van Madhavan and @Anon Null This was a real Atlassian-side bug in Rovo Dev CLI v0.13.46. Atlassian confirmed the new file-locking mechanism caused the config.yml.lock could not be acquired error, and said it was fixed in v0.13.47. So the right advice is to update to the latest Rovo Dev version and retry rather than keep…

@Georg Fankhauser This is a known limitation rather than a prompting issue. Rovo (and Confluence rendering) doesn’t reliably support nested formatting like bullet lists inside table cells, especially when generated via AI. Even with correct syntax, lists often break or render as plain text. A workable approach is to force…

@maurodomenicoabeni to add to Rebekka's comment, this looks like a known issue where connector state gets stuck on the Atlassian side rather than a user error. If it’s been stuck for hours, it likely won’t resolve on its own. Try refreshing, clearing the browser cache, or removing/re-adding the connector from another admin…

@gki welcome to the community. You’re not alone—multiple users reported Rovo disappearing from Confluence around that time, which suggests this is often tied to rollout changes or temporary feature flag issues rather than something you did. In addition to checking admin settings and licensing, it’s worth confirming your…

@Ian Goquingco welcome to the community. For best results, write epics with clear outcomes, user value, and defined scope (who, what, why). Include acceptance criteria, key workflows, and constraints. The more structured and specific the epic, the better Rovo can generate meaningful stories. Avoid vague goals—focus on…

@Ruth MorenoRebekka’s response is on the right track, especially about limitations with Assets fields and non-configurable safety filters. That said, the issue here looks less like a prompt problem and more like a data formatting one—Jira Assets expects a structured object, not just an ID, which explains why [object…

To add to @Rebekka Heilmann _viadee_ Atlassian has been transitioning toward Rovo-powered agents, which are separate from legacy Virtual Agents. Availability of Rovo Agents in the customer portal depends on Rovo enablement + rollout (Service Collection), not just plan tier—and rollout is still uneven.

To add to @Rebekka Heilmann _viadee_ mention of the official documentation; @Dibyakanta Barik for a Node server, you can connect with an MCP-compatible client such as @modelcontextprotocol/sdk, but you must follow the Rovo MCP OAuth 2.1 setup rather than reuse a standard Atlassian OAuth 2.0 token. Atlassian also documents…

Hey ya'll this looks like an intermittent Atlassian MCP reliability issue, not just a bad local setup. Multiple users reported the same “We are having trouble completing this action” error, and Atlassian has acknowledged MCP reliability problems for some users. If it persists, fully restart Claude/VS Code, kill lingering…

@Student this once pops up in the Champions Slack channel every month with mixedd experiences. Rovo is not included by default in all Teamwork Collection or Jira plans. Even if Atlassian Intelligence is available, Rovo (Search/Ask AI) requires separate enablement and may still be in limited rollout or require admin…

@nguyenntt welcome to the community. To add to @Jovana Dunisijevic request, this may have been a transient Rovo Dev service issue around that time, since Atlassian’s status page shows a Feb. 13, 2026 incident where Rovo Dev was not starting and was later resolved. If it still fails, verify you’re signing into the correct…

@Ronit Gieske to add to what @Rebekka Heilmann _viadee_ mentioned, currently Rovo connectors (including Zendesk) do not support native date-range filtering at the sync level. Syncs typically ingest all accessible data, with filtering handled at the search/query stage rather than during indexing. As a workaround, you can…

@Milani Dick Yes—others reported the same behavior on Feb. 13, 2026, so it does not look isolated. For now, using saved image files instead of clipboard paste is the safest workaround, and sharing the exact OS/app version with support should help them reproduce it.