Dr Valeri Colon (Connect Centric) Community Champion

@Vysakhan Sreekumaran Kasthuri nice catch—that aligns with what others are seeing too. The rename to searchAtlassian / fetchAtlassian does look like part of a broader standardization effort, likely to make tool naming more consistent across MCP. That said, these changes haven’t always been clearly documented, which is why…

@Arkadiusz Wroblewski I agree—this really comes down to expectations. Rovo is powerful, but it’s still context-driven, not deterministic. If you need “always list every attachment exactly,” that’s more of a system/process requirement than something AI can reliably guarantee today. It can look stable until a model shift…

Welcome to the community all! @Tal Fadlon You can’t convert a Rovo agent into a standalone Slack app, but you can use it in Slack via the Rovo Slack integration. Install the Rovo app in Slack, link it to your Atlassian site, and your agents can respond there. No separate packaging or deployment like a traditional Slack…

@ahmed mohamed you’re right to question this—each Rovo Dev “Standard” entry is a separate subscription, so yes, they can each be billed if not canceled. It looks like multiple sites/subscriptions were created, which is why you’re seeing several charges. To fix: Go to admin.atlassian.com → Billing → Subscriptions Cancel the…

@Trudy P Claspill for the win! This isn’t a URL issue. Atlassian support only recognizes sites and products tied to your account + permissions. If you only see Bitbucket, it means your account isn’t recognized as having access (or admin rights) for Jira/Confluence/Rovo in the support system. Also, Rovo Dev doesn’t always…

In other words @Dirk... in automation rules, Rovo agents can analyze and return output, but they can’t directly create, update, or delete content. Atlassian documents this limit for agents in automations, so the workaround is to have the agent return something structured with {{agentResponse}}, then let native Automation…

Hi @Placid Cardoz Yes—this is a realistic pattern, with one nuance: VSA is the better fit for the step-by-step form experience, while Rovo helps with knowledge, FAQ answers, and request creation. In Jira Service Management, the virtual service agent can gather information conversationally using flow steps and fields, then…

@sankaracourtallam_rathinasabapathy welcome. And I agree with @Arkadiusz Wroblewski I’d be careful calling this a confirmed regression. Rovo’s handling of Jira attachments isn’t fully consistent today, especially when relying on model interpretation rather than explicit retrieval. What you’re seeing (attachments in…

@Jazor He welcome to the community. You’re not alone—this looks like a recent auth loop issue with MCP, especially if it was working before. The “stuck on Accept” screen + repeated failures usually points to a session/OAuth issue, not your config. Try: Logout/login to Atlassian, then retry Use a different browser or…

@Vysakhan Sreekumaran Kasthuri welcome to the community. There isn’t a single, fully up-to-date public list of MCP endpoints or tools right now. What you see available depends on your authentication method, scopes, and MCP version, which is why endpoints like search or fetch may disappear. The best way to see what’s…

Hi @Charlene Freeman you can increase the limit by duplicating or editing the agent, but the 20-item cap is there to help maintain response quality and stay within model limits. If you raise it too much, you may see slower responses or weaker summaries. In practice, it works better to split larger releases into smaller…

@Marcia Isabel Mota welcome to the community. @Maja Vallin is leading you on the right path, this is a known limitation. Rovo in JSM is primarily designed for internal users (agents), and support for external customers in the portal is still rolling out and not fully available yet.

Welcome to the community @PERUMALLA BALA THIRUMALA SAI VINAY SUKHESH A 403 with Rovo in Confluence is almost always an entitlement or permission issue, not a bug. Check: AI/Rovo enabled → Admin → Apps → AI settings User has product access (Confluence) + Rovo access Any org-level restrictions or policies If it’s happening…

Good catch @zach_morgan —this is a common gotcha. Rovo MCP doesn’t currently support Bearer token auth for this setup, so it falls back to read-only tools. That’s why you only saw getTeamworkGraph methods. Switching to Basic auth (email + API token) enables full access, including write operations like creating Jira issues.…

@Diem Chau welcome to the community. @Brant Schroeder has pointed you in the right direction. That error usually means your Slack workspace isn’t properly linked to an Atlassian cloud site. Rovo for Slack needs a valid cloud ID mapping, which can fail if the app wasn’t fully authorized, the wrong site was selected, or the…

@Iain Phillips welcome to the community. You may not be missing a step in Rovo itself. For Generate code, the repo picker only shows repos that are usable by Rovo Dev in Jira, not just repos the GitHub connector has indexed. The repo needs to be GitHub Cloud, under 20 GB, you need read/write access, and for private repos…

@sumi takashi welcome to the community . This sounds like two separate Windows-specific issues, and neither looks like user error. For SSL, Atlassian’s docs don’t show a supported way to pass a custom CA bundle into Rovo Dev CLI, so behind Zscaler it may fail unless the cert chain is trusted by the environment the CLI…

这个问题通常不是配置错误，而是由于中国大陆网络访问 Atlassian Cloud 的限制导致的。 常见情况： 访问或创建站点时连接不稳定或失败 某些服务被限制或延迟较高 可行方式： 使用稳定的网络环境（部分用户会用 VPN，但需符合公司/当地合规要求） 或联系 Atlassian 本地合作伙伴协助创建和配置 如果持续失败，也建议提交支持工单确认是否为账号或区域限制。

@Victor Tan I get the frustration—Rovo Dev actually can’t be fully uninstalled from a site today. It’s part of the platform, so the best you can do is cancel billing and disable its features. Even then, some UI elements may still appear. If you truly need it removed, the only option is to contact Atlassian Support, as…

@Ethan Melsheimer and @Bryan Stephens welcome to the community. [Sadly] even if the status page shows “no issues,” Rovo incidents can lag or go unreported initially. Swathi from the Atlassian team confirmed an active incident in other threads around this timeframe. If everyone on your site is seeing this, it’s almost…

@Mayra welcome to the community. Swathi from the Atlassian team confirmed an active incident in other threads around this timeframe. If everyone on your site is seeing this, it’s almost certainly Atlassian-side, not your setup. Best move: monitor or raise a support ticket with timestamps.

Welcome to the community @Dylhoff_ Joel You can get partway there, but not fully in one seamless step today. Rovo can draft the content and, with the right skills, create Jira work items, but JPD template/field completion is still limited and not always reliable from chat alone. If you need it to consistently create the…

Welcome to the community @Maniteja Varanasi Your config is close, but the main thing to check is whether API token auth is enabled by your org admin for Atlassian Rovo MCP. If it isn’t, browser auth is required and token-based setup will fail. Also, NODE_TLS_REJECT_UNAUTHORIZED=0 only bypasses cert checks; it won’t fix…

@Miya welcome to the community. This looks like a Windows encoding issue, not something you did wrong. Rovo Dev/ACLI doesn’t handle cp932 well in some cases, especially during startup. Right now there’s no clean way to force UTF-8 just for the CLI without changing system settings. I’d treat this as a bug—best next step is…

@james welcome to the community. You’re not alone—this has been a known mismatch issue between Admin UI and CLI. What’s happening: Admin shows allocated credits (2000) CLI reflects usable credits tied to your auth/session/site context Common causes: CLI authenticated to a different site/org Entitlements not fully synced…

@Simon Brizuela welcome to the community. This has been a known issue with Rovo Dev credits not applying correctly after signup/upgrade. Some users hit “credit limit reached” even though they should have the 2,000 included credits—usually due to provisioning delays or entitlement mismatch. A few things to try: Check /usage…

@Raj welcome to the community. You’re hitting a real limitation—Rovo struggles with required fields, and Assets fields are one of the hardest since they require valid object IDs (not just text). Right now, Rovo can’t reliably: Look up Assets values Select the correct object Populate required Assets fields Workarounds:…

@Charles Liss you’re not imagining it—today, Rovo’s Jira access is mostly limited to issue-level fields. While it can read component names, it typically doesn’t reliably access or use component descriptions in responses. This is a known gap rather than a configuration issue. If this is important for triage, a workaround is…

Hey @Alex Edghill and thanks @Trudy P Claspill You’re right to expect it to disappear, but this is a known quirk. A few key points: Rovo Dev is site-level only (can’t remove per issue/project) Disabling in AI settings is correct, but the panel may still show temporarily This can be due to feature flags, rollout state, or…

Thanks @Tomislav Tobijas for the moooove. @David Gerrard this is probably not just you. Atlassian’s MCP docs say that when nothing happens or results are partial, common causes are auth/session expiry, missing scopes, or permissions, and they recommend re-authenticating and checking logs. For your query specifically, try…