❓ Rovo Q&A Highlights: Top Contributors & Issues❓

[#1]

Thank you to everyone helping users navigate a platform that’s evolving quickly with frequent new capabilities. The community continues to play a key role in adding clarity and real-world context.

🌟 Top Contributors - Last ~30

Observed Trends since Leaderboard is no longer visible on Q&A forum

🥇 @Rebekka Heilmann _viadee_— Dominates accepted answers across agents, integrations, and general troubleshooting. High accuracy + fast responses.

🥈 @Trudy Claspill — Consistent resolver for admin, billing, permissions, and support-path questions. High acceptance rate.

🥉 @Tomislav Tobijas — Strong in MCP, limitations, and routing users to the right next step. Frequently accepted in edge-case threads.

🏅 @Kai Krause — Technical clarity on automation boundaries and platform constraints. Accepted where deeper explanation is needed.

🏅 @Christopher Yen — Practical troubleshooting, especially around agents and configuration gaps.

Observed patterns show a clear concentration of accepted answers among a small group of highly active contributors. Cheers to your dedication.

Key Themes

Agent Limitations in Automation & Actions
Users expect agents to execute, but in automation they can only reason and return output. Creation and updates must still be handled by native automation or APIs.

Entitlements, Billing & Provisioning Confusion
Frequent issues with credits, access, subscriptions, and missing products. Many trace back to backend provisioning delays or permission mismatches.

Rovo Dev + MCP Instability
Auth loops, read-only tool limitations, missing endpoints, and timeouts continue to surface. MCP is powerful, but still inconsistent.

Slack & JSM Integration Gaps
Limitations in portal access, Slack behavior, and ticket flows reveal hard platform constraints.

Connector Behavior & Data Access Misunderstandings
Admin controls don’t always behave as expected (e.g., user OAuth bypass), and some data remains inconsistently accessible.

UI Bugs & Inconsistent Behavior
“Unknown error,” missing features, and rendering issues often tie back to rollouts or backend instability.

Overestimation of AI Capability
Users expect deterministic, system-level behavior, but Rovo remains context-limited without explicit APIs.

Emerging Pattern: Support Dependency

Based on a broad sample of threads from this timeframe, roughly 1 in 3 Rovo questions ultimately require Atlassian Support due to entitlement, provisioning, or bugs rather than configuration issues.

The community is increasingly acting as a triage layer, not a resolution layer. A large portion of issues are:

• Not user error
• Not documented clearly
• Not fixable without Atlassian intervention

Many thanks to the Atlassian team for actively jumping in to confirm incidents and known issues- the visibility goes a long way.

💡 How You Can Help Keep the Community Strong

• Upvote helpful answers so patterns surface faster

• Accept answers once resolved—it helps everyone

• Search first; many issues share the same root cause

From me (Group Leader for the Rovo Q&A Forum, Community Champion and Atlassian Service Partner) 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. 💙

This post marks the end of the Q's I've reviewed in this round.

[Rebekka Heilmann (viadee)]

Thank you @Dr Valeri Colon _Connect Centric_ for keeping this community organised and chiming in whenever you're expertise is needed!