Thank you to everyone helping users navigate a fast-growing AI platform that’s evolving weekly. Your explanations, troubleshooting, and honesty continue to set the tone for a supportive, high-signal community.
🌟 Top Contributors - Last 30 Days
🥇@Rebekka Heilmann _viadee_ — Clear, detail-rich guidance across agents, knowledge, and workflows.
🥈@Tomislav Tobijas — Excellent deep-dives into MCP, connectors, and protocol behavior.
🥉@Mohanraj Thangamuthu — Reliable, authoritative answers on product limits and design intent.
🏅@Alex Gallien — Strong technical insight, especially across agent behavior and platform boundaries.
🏅@Trudy Claspill — The community’s steady compass for where and how to file feature requests.
Agent Reliability & Gaps
A wave of questions centered on inconsistent outputs—agents missing issues, failing to enforce rules, or hallucinating. Users learned Rovo can’t yet guarantee determinism, deep pagination, or access to full Jira history or development metadata.
MCP Instability & Spec Mismatches
Multiple threads reported timeouts, session drops, discovery failures, and OAuth inconsistencies. MCP support remains uneven, with /v1/sse and /v1/mcp showing intermittent failures and incomplete RFC 9728 compliance.
Connectors Not Indexing (SharePoint, Google Drive, Custom Sites)
SharePoint sync delays, Google Drive’s all-or-nothing scope, and strict crawl rules blocked indexing for many. Users highlighted missing logs and the need for clearer visibility into indexing progress.
Slack, Portal, & JSM Integration Limits
Custom agents in Slack can’t read thread history; portal agents can’t skip the “Raise request” confirmation; and VSA flows can’t auto-create tickets. Many discovered UI safeguards override agent intent.
Missing Skills & Unsupported Operations
Users sought capabilities like logging work, linking issues, editing JPD drafts, or dynamically selecting knowledge. Many of these remain unsupported, even for admins.
Model Failures & Opus 4.6 Outages
Repeated “Failed to generate LLM response” errors confirmed backend instability for certain models. Switching models was often the only workaround.
Pricing, Credits & Governance Questions
With Rovo Dev credits going live, many asked about pricing, credit usage, tenant differences, and cost transparency—highlighting a need for clearer guidance before rollout.
Users Overestimating Rovo’s Access
A recurring pain point: Rovo can’t access everything a user can. Limits around changelogs, PR metadata, development panels, attachments, and hidden fields surfaced repeatedly.
Upvote helpful answers so patterns surface faster
Accept answers once resolved—it helps everyone
Search first; many issues share the same root cause
From @Kelly Stocker (Atlassian's Rovo Community Manager) and me (Rovo Community Champion): thank you for your curiosity, patience, and collaboration. Every question and every accepted answer helps the entire ecosystem learn faster and adopt Rovo more effectively. 💙
Please Note: In the community we’re happy to help troubleshoot your custom agents. If you need full agent instructions, we encourage you to take a course through Atlassian Learning or Community-Led Learning, or work with an Atlassian Partner who can support you through a statement of work.
(This post marks the end of the Q's I've reviewed in this round)
Dr Valeri Colon _Connect Centric_
6 comments