Dr Valeri Colon (Connect Centric) Community Champion

@Zenith Admin welcome to the community. If “Ask Rovo” isn’t responding (no output or generic error), a few common causes to check: Site-wide issue → ask if others are seeing it too AI/Rovo disabled → Admin → Apps → AI settings Browser/session issue → hard refresh or try another browser Permissions → confirm the user has…

@Daichi Nakagawa _ 中川 大地 _ this looks like a known UI rendering issue in Rovo Chat, not something you can control via settings. A few quick checks: Try a hard refresh / different browser Disable extensions (some affect layout) Zoom level (100%)—Rovo UI can behave oddly otherwise If it persists across users/browsers, it’s…

Hi @ElEscarabajo this usually isn’t a “bug,” but an entitlement or provisioning mismatch. Common causes: Subscription is active, but entitlements haven’t propagated yet You’re on Premium, but not assigned access to Rovo Dev features Wrong site/account authenticated in CLI or UI Also, there’s no known “9-day cutoff”—that’s…

@jefferson_ulloa you’re running into a couple of real Rovo limitations—not just prompt issues: Agents don’t truly “copy pages” → they recreate content, so formatting (tables, spacing) often breaks Template fidelity isn’t guaranteed, even if the page is linked Page location control is limited → many cases default to space…

@Mike Craig welcome to the community. There’s currently no out-of-the-box connector for GitLab self-hosted in Rovo. If you want to integrate it, your main option today is to build a custom solution using Forge with Rovo actions, which allows you to call GitLab APIs directly. This requires that your GitLab instance be…

Hi @Mario today, those 👍 / 👎 buttons are part of Atlassian’s built-in feedback mechanism and aren’t configurable. You can’t change the buttons, customize the feedback flow or trigger actions directly from them. They’re used internally to improve responses. If you need custom behavior (e.g., escalation, follow-ups), you’d…

@Armen Gevorgyan welcome to the community. A few things to check—this is usually entitlement or rollout related, not setup: AI/Rovo enabled → Admin → Apps → AI settings (you’ve done this 👍) User has access → not just site-level, but user-level entitlement Rollout status → Rovo Chat is still rolling out; some Premium sites…

Hi @kui niu you’re not alone—this has come up before, but it’s rarely a confirmed “model swap.” In Rovo Dev: Model routing can vary by context, limits, or fallback behavior Quality changes can come from prompt structure, tool use, or updates (like your version bump) There’s no user-facing way to verify the exact model per…

@John Ginn welcome to the community. Short answer: you can’t currently enforce full regional processing for Rovo/MCP. Data residency (stored data) → can be pinned for Jira/Confluence Rovo/MCP processing → not region-pinned LLM processing → may occur outside your region (e.g., US-based providers) Also, MCP isn’t just a…

@Muhammadjon Saidov sorry you’re running into this—this is frustrating, but you’re not stuck. Rovo Dev billing is managed via Atlassian Admin, not inside Rovo itself: Go to admin.atlassian.com Select your site Go to Billing → Manage subscriptions Find Rovo Dev / AI subscription Cancel or downgrade If you don’t see it, you…

Hey @Mario ! @Rebekka Heilmann _viadee_ answer is directionally right, but a little outdated. You don’t need a custom JSM API integration for this now. Atlassian’s current flow is the Raise a request skill, and when the user submits it from Slack, the agent can post a link to the created JSM work item in the Slack thread.…

Hey @Charlie Misonne Partly a prompting issue, but also a product limitation. Rovo’s support for Jira custom fields was improved, but field retrieval is still inconsistent in practice—especially when you need a custom field from a linked issue rather than the source issue itself. Atlassian has acknowledged custom-field…

Greetings @- If this is affecting multiple users across Jira + Confluence, it’s almost always a Rovo backend incident, even if the status page is green. Quick checks: Confirm AI/Rovo still enabled in Atlassian Admin Try a different browser (to rule out session issues) If still failing, don’t troubleshoot further—raise a…

@Eric Gurin this “unknown error” is fairly common with Rovo agents right now—usually not your config, but validation failing silently. A few things to check: You have Rovo + Agent creation permissions AI/Rovo features are enabled on the site Try removing any external connectors or tools temporarily Check for unsupported…

@asdasd welcome to the community. To tighten up @Himanshu Tiwary response... This does look like an entitlement issue, but a few Rovo Dev specifics to check: Rovo Dev must be enabled on that exact site (not just Jira active) Your user must have Rovo access + product access (Jira/Confluence) Make sure CLI/VS Code is…

You’re not missing anything—this is a current limitation, not a setup mistake. The Rovo Slack app requires a real Atlassian user because it operates on behalf of a user identity (permissions, content access, audit). Service accounts aren’t supported for this flow today. Workarounds: Use a dedicated “bot” user (licensed)…

I can confirm @Tomislav Tobijas response. This is a current product limitation, not something wrong with your prompt. With the available custom agent page-edit skills, content is appended to the bottom rather than inserted under a specific heading or into a specific layout section. So changing the page layout or using…

Great list—one thing I’d add @Brian Wu is using it as a bridge between code and context. For example: pull a Jira ticket, summarize requirements, then draft code or tests aligned to it. Also useful for quick scripts, PR reviews, and CLI-driven debugging loops. The real value comes from chaining small tasks together rather…

The responses are heading in the right direction @Deepak Chikane Based on your tests, this doesn’t look like a schema or setup issue anymore. Since all tools load but fail at execution, it points to either auth/context issues (token format, scopes, admin settings) or a platform-side MCP runtime issue. The “Cannot read…

@adssadasd welcome to the community. This looks more like a known Windows Rovo Dev packaging issue than a local Python problem. Since the CLI bundles Python/NumPy, the usual NumPy reinstall advice doesn’t really apply. A clean reinstall is worth a quick try in case the update was incomplete, but if it started right after…

@ma_rovere welcome to the community. This looks like a Rovo Dev Windows regression, not something you caused locally. Since the CLI bundles Python/NumPy, generic NumPy reinstall steps don’t really apply here. A clean reinstall may be worth a quick try in case the update was incomplete, but if it started right after the CLI…

Just to add—since this is Early Access, availability can still depend on your Teams tenant settings and admin approvals. If you still don’t see it in search, installing via direct link or having a Teams admin approve the app is often required.

@YOHAN Totally understand the frustration—what you’re describing aligns with a known issue during the recent Rovo Dev credit changes rollout, where users were incorrectly blocked with “limit reached.” This wasn’t expected behavior. While support is the right path, it would help to acknowledge this as a broader incident…

@camila_medrano welcome to the community. Inviting the Rovo app can help, but this is usually about identity context mapping between Slack and Atlassian. If users aren’t properly matched (email/domain mismatch, guest users, or missing permissions), Rovo may default to the admin context. Make sure Slack users are correctly…

Hey @Shane Lacey while it’s unlikely Rovo intentionally moved/archived the page, what you’re describing aligns with how Confluence handles parent/ancestor changes—a page can appear “missing” if its parent changed or was removed. Also, Rovo doesn’t always have full visibility into structural metadata after actions, so its…

@davyn you’re not alone—there have been recent issues and changes affecting site creation, especially for Rovo Dev. In many cases, this isn’t user error but a backend provisioning issue (often with a Trace ID). If you’re seeing generic errors, support is the right path—but it’s not just “requirements,” there have been…

Hi @Tijs Vrolix This isn’t something you can fully control today. These responses are triggered by LLM safety filters (both Atlassian + underlying model), and they can be overly sensitive to finance/legal wording—even when the use case is valid. Prompt tweaks can sometimes help (e.g., adding business context), but you…

@lavdaa lehsaan welcome to the community! This isn’t expected behavior. Atlassian confirmed there’s been a bug during recent changes to Rovo Dev credits, especially affecting new accounts with billing added. So seeing “limit reached” with 0 usage is not normal and not due to other users. If it’s still happening, raise a…

Just to confirm for others—this isn’t expected behavior. Atlassian has acknowledged this as a bug during recent credit changes, especially for new accounts with billing set up. So seeing 0/2000 credits with 0 used is not normal. If it persists, raise a support ticket so they can fix it on the backend.

This is a known type of backend provisioning error, and the Trace ID is key for Atlassian to investigate. One thing to check first—sometimes the site actually gets created despite the error, so review your email or existing sites. If not, you’ll need to contact support and include the Trace ID, as this isn’t something that…