Thank you to everyone contributing during a period with a noticeable increase in activity, experimentation, and platform changes. This timeframe reflects both growing adoption and the realities of a product still maturing.
🌟 Top Contributors (Observed)
🏅 @Arkadiusz Wroblewski — Emerging as a leading contributor with consistent, practical answers across MCP, agents, and platform limitations.
🏅 @Fabio Racobaldo _Catworkx_ — Strong presence in activation, rollout, and admin-related troubleshooting.
👏 Notably, there’s been an increase in new contributors, expanding both the range of topics covered and perspectives shared.
🏅 @Rebekka Heilmann _viadee_ — Continues to provide thoughtful, structured responses across complex scenarios.
🏅 @Tomislav Tobijas — Reliable in guiding users through integrations and next steps, especially with MCP.
🔑 Key Themes
Agent Capabilities vs Expectations
There is strong interest in using agents for execution-heavy tasks (ticket creation, updates, workflows). In practice, agents are more reliable for reasoning and drafting than for consistent action execution, leading to some friction.
Action Reliability & Validation
A recurring pattern: agents sometimes report success without completing the action. This has led users to adopt verification steps or fallback to automation/APIs for critical workflows.
Rovo Dev & Entitlement Confusion
Questions around CLI access, model availability, and trial vs paid behavior remain common. Most issues trace back to entitlements, rollout timing, or plan differences, rather than misconfiguration.
MCP: High Interest, Mixed Experience
MCP continues to generate interest for integrations and developer workflows. At the same time, users report:
- Auth inconsistencies
- Limited write capabilities
- Session instability
This reflects a feature set that is powerful but still evolving.
Automation + Agent Boundary
There is clearer understanding forming that agents don’t fully execute within automation. Effective setups combine:
- Agents for reasoning
- Automation/API for execution
Platform Instability (April 14 timeframe)
There was a noticeable spike in issues:
- Missing agents / blank configurations
- Studio loading problems
- API/HTTP errors
These were largely tied to incident/rollout behavior, not user setup, and resolved over time—but impacted confidence during that window.
Emerging Patterns
This period reflects steady growth in adoption, with more teams testing real-world use cases—alongside some expected friction as the platform continues to evolve.
- A notable portion of issues still require Atlassian Support, especially around entitlements, rollouts, and backend behavior
- Users are shifting toward a hybrid approach:
- Rovo for drafting and insights
- Structured systems (automation/APIs) for execution
- Light validation for accuracy
Overall, expectations are becoming more aligned with current capabilities, with the community continuing to help bridge the gap between what Rovo can do today and what users expect next.
💡 How You Can Help Keep the Community Strong
- Search first; your question may already be asked & answered
- Upvote helpful answers so the best solutions rise to the top
- Accept answers once resolved—so others can quickly find what worked
As always thank you for your curiosity, patience, and collaboration. Every question and every accepted answer helps the ecosystem learn faster and adopt Rovo more effectively 💙
This post marks the end of the Q’s I’ve reviewed in this round.
