Dr Valeri Colon (Connect Centric) Community Champion

@Fabio Genovese _ArtigianoDelSoftware_ we’d make magic, no doubt. The Champion Slack channel always pushes me to think a level deeper, and this was definitely one of those moments. Imagine what we’d come up with in a live session or whiteboard moment—might have to make that happen...

@Ryan Boyd you’ve essentially added a 5th workaround—attaching images directly in chat. In your use case, you’re leveraging Rovo with image-capable models in a specific workflow (explicit image input → model analyzes it), rather than Rovo passively analyzing images in Confluence pages (retrieving indexed content that…

@Sumit Mahajan if you can see the tools but can’t call them, that usually points to auth format or permission scope, not token expiry. Make sure you’re using Basic auth (email + API token), not Bearer. Also check: the user tied to the token has Jira permissions to create issues MCP is enabled for your org/site If those are…

@Jorge Cammarota Sem problema—boa exploração! Quando tiver a chance de testar, vai ser ótimo trocar ideias e ver o que funciona melhor.

@Lan Dang _Tyme_ this is expected right now. Custom agents in Slack don’t reliably receive the full message context—even for a single message—when triggered via emoji/workflows. Your two options are to (1) Authorize Slack MCP so it can fetch the message with proper permissions/context or (2) Pass the message link/timestamp…

@Mohammed Suhail you’re hitting a mix of limitations + how Rovo resolves context today. Child pages: It can create pages, but parent placement isn’t reliable from chat alone. Even with instructions, it may default to the space unless the parent is clearly resolved (link/ID). Charts: Tables are more reliable. Charts depend…

@Ayush Srivastava Rovo is not universally included across all paid plans in the same way. What you’re seeing as “premium feature” usually means one of these: Your org doesn’t currently have Rovo enabled (rollout or region) You’re on a plan where Rovo is not included by default or requires activation Your trial ended or…

@Habib ZOUARI appreciate you sharing that—what you’re seeing is pretty consistent with how others are hitting the edges right now. You’re right, chunking solves the truncation problem, but shifts complexity to orchestration and consistency. Today, the most reliable pattern I’ve seen is combining: bounded generation per…

@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.

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…

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…

@Andrea Daniels Your frustration makes sense—this one isn’t something the community can fully resolve. You’re currently in the Atlassian Community (peer support), not direct Atlassian Support. I did flag your post using the “Request support” option, so it’s now in their queue. If you want to contact them directly for…

@Andrea Daniels welcome to the community. This usually comes down to entitlement sync, not billing. Your screenshots show Standard + invoice, but also 0 users assigned, which means the license isn’t actually applied to your account. Make sure: You’re in the rovo-dev-agents-users group The site shows >0 licensed users…

@joe hattab that can happen even after upgrading. Model selection in Rovo Dev CLI depends on your plan, entitlements, and rollout, not just payment. Some orgs are still limited to a default model until additional models are enabled. If you just upgraded, it can also be a sync delay. If it doesn’t change after a bit, worth…

@Maurice Adams what you’re seeing can happen—Rovo may say it created a ticket even when the action failed. It’s usually due to missing required fields, permissions, or validation rules, and the failure isn’t always surfaced clearly. Best practice: add a confirmation step (retrieve the issue after creation) to verify…

@Mario That can happen even if your agent is only quoting Confluence. Rovo still applies Atlassian’s AI safety filters, and prompts about medical aid, dependents, newborns, plan changes, or deadlines can be interpreted as health/benefits advice involving sensitive personal data. So this is usually a policy-triggered false…

@Yashodip Jadhav great question—and you’re not alone. Rovo is best seen as assistive, not authoritative. It can speed up drafting, summaries, and exploration, but validation is still required, especially for structured data or decisions. Most teams see gains when they use it for first drafts and context gathering, not…

Note: access can vary based on entitlements and rollout. Keep shining bright like a diamond @Arkadiusz Wroblewski 

@LOIK BIOIJ yes—this can happen and it’s not always just “free vs paid.” Model access in Rovo Dev depends on your specific plan, entitlements, and rollout. Even on paid plans, some models (like newer Claude versions) may not be enabled yet. The fallback behavior is expected. If you’re on a paid plan and still blocked, it’s…

@Joachim Aßfalg welcome to the community. Just to clarify a couple of points—Rovo Dev isn’t automatically available to everyone on Premium. It depends on entitlements and rollout, and while you may see trial credits, full CLI/MCP access typically requires Rovo Dev Standard to be active on the site. Also, the “Allow user…

@Ayush Srivastava welcome to the community. Just to clarify one point—this likely isn’t due to a model migration removing your agents. Around April 14 there was a Rovo incident that caused issues like missing agents, blank configs, and access errors. The “Activate AI” message usually means AI was toggled off at the org…

@Satbir adding to what @Fabio Racobaldo _Catworkx_ said—rollout is part of it, but also double check eligibility and activation conditions: Rovo is only available on certain plans and regions It may require AI features to be enabled under admin settings Some trials don’t include full Rovo access If it’s not visible after a…

@Karl Adrian Carpio I'd add... Rovo Dev can make code changes on a branch and create a draft pull request in specific Jira/automation workflows, but that capability is separate from the GitHub skills available to general Rovo agents. So if you’re asking about a normal Rovo agent pushing/committing files directly via GitHub…

@Baojian Zhang sometimes this happens due to permission sync delays or missing group/page-level access even after approval. Have them confirm: You’re in the correct Confluence permission group The page has explicit access for that group Try logging out/in or waiting a bit (can take time to propagate) If all that looks…

@Thais Tokomantel welcome to the community. Adding a bit more context—GitHub Copilot doesn’t natively support MCP the same way tools like Claude Desktop do. So even if your API token is correct, the integration may not work as expected. If you’re trying this via VS Code, you’ll typically need Rovo Dev (not just MCP) or a…

@Martin Cassidy adding to @Rebekka Heilmann _viadee_’s point—you’re not imagining it, but it’s less about “different models” and more about how tools are invoked. In Chat, Rovo can directly call internal tools (like PRs/deployments), while agents only use the skills you explicitly give them. If those exact tools aren’t…

@Tomislav Tobijas Best quote of the month "[note: text might look AI-ish because I CBA with writing everything from scratch] " 

@Christian Holton I’d add one nuance to @Arkadiusz Wroblewski’s answer—while MCP respects permissions, it can still perform write actions within that scope, and capabilities can evolve. So it’s best not to assume certain actions (like delete) will always be unavailable. Also, recovery isn’t uniform—projects, issues, and…

@Matt Riti adding to what @Ajay _view26_ mentioned—also check a few other common causes. Rovo visibility can be affected by AI settings (Apps → AI settings), recent feature rollout changes, or even temporary outages. I’ve also seen it disappear due to browser caching/session issues, so a refresh or incognito test is worth…

@Mathew Lederman I get the frustration. When JAC tickets like ROVO-119 are closed, it usually means the feature is considered delivered or addressed internally—but that doesn’t always mean documentation is complete or clear yet. JAC isn’t used for ongoing discussion, which is why comments get locked. For gaps, the best…