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

[#1]

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.

[Dr Valeri Colon _Connect Centric_]

For context, I usually end these posts with a quick note

from me as Group Leader for the Rovo Q&A Forum, Community Champion, and Atlassian Service Partner

so it’s clear this isn’t coming from a random observer. I started teaching Atlassian Intelligence and later Rovo before they were announced at Teams.

In those early days, many community questions went unanswered because no one really had the answers yet— a challenge in supporting emerging technologies. Frustration grew and still grows on occasion. I committed to helping people adjust to the distributive shifts caused by AI in how we work and in the industry overall.

Over time, more community members have joined in. These posts are also meant to recognize and thank the brave who step up and offer support, even when it’s not easy.

[Dr Valeri Colon _Connect Centric_]

More than summaries, these posts help surface patterns—what’s working, what’s not, and where others are getting stuck—so users don’t have to start from scratch. For Atlassian, they provide a consolidated view of real-world friction points and recurring gaps worth paying attention to.

On appropriate AI use, one of the most practical approaches is to use it as a support layer, not a replacement. I reference a custom AI agent I designed to pull from official sources and self-authored articles to stay current, and I encourage others to sense-check their responses the same way. Even a simple prompt like: “Spell and grammar check my response while ensuring it’s factual, up-to-date, and succinct” can improve clarity and confidence. This also serves as part of my disclosure to align with the revised Atlassian Rules of Engagement: 

AI usage for the purpose of formatting, language, spelling, etc. is allowed if utilized as a tool, but the core of your contributions should be written by you. AI should not be used as a substitute for providing accurate answers and knowledge to our users, and you are responsible for ensuring that any information you provide is accurate. If you post images or text wholly or largely generated by AI, you should also indicate as such in your comments. For more, please refer to Atlassian’s Responsible Tech Principles.

[Rebekka Heilmann _viadee_]

Thank you @Dr Valeri Colon _Connect Centric_ as always. You are the glue that keeps it all together!

Glad to see I've still made it despite my PTO ;)

[Dr Valeri Colon _Connect Centric_]

@Rebekka Heilmann _viadee_ I don't know where you found the time this round, but I appreciate every response. It was an easy review. You and @Tomislav Tobijas are still hanging on to the top spots.