Comments
-
Welcome to the Community, @Vikas K Sinha Yes, given that you've already reauthenticated, cleared browser data, and reinstalled the application, this appears less likely to be a local client issue and more likely related to account provisioning, authorization context, or a backend service issue. At this point, opening a…
-
Welcome to the Community, @Jarek Olchowik. This sounds like an excellent fit for a direct conversation with Atlassian, especially given the regulatory, security, and residency requirements involved. The "ticket → code change → draft PR" workflow is one of the primary scenarios Rovo Dev is designed to support, but details…
-
@Andrew welcome to the community! In my experience, this is usually a shared process rather than something owned entirely by JSM. JSM often serves as the front door for requests, approvals, and audit records, while IAM/IGA platforms handle provisioning, deprovisioning, recertification, and enforcement. Security, Legal,…
-
Hi @Isabel Calzada In Rovo, instructions tell the agent how to behave, knowledge sources tell it what information it can reference, permissions control who can use or manage it, and Skills define what actions it can take. For example, a Skill may let an agent search Jira, create a Confluence page, comment on an issue, or…
-
Hey @Cam Briggs to add to this -- SAP LeanIX does provide an official MCP Server, and Atlassian Rovo supports external MCP connections. However, I haven't seen any documentation confirming that the LeanIX MCP Server has been validated with Atlassian's External MCP implementation. Since both products implement MCP, they…
-
Hi @Piyush Mathur I agree with @Yashodip Jadhav. I haven't seen any documentation suggesting that Rovo Dev slash commands can currently be scripted or invoked from custom prompts. If Atlassian wanted to enable this, my assumption is that the Rovo Dev team would need to expose those commands as supported actions that…
-
@Luis Gallardo Cortés, bienvenido a la Comunidad. Si "Preguntar a Rovo" desapareció repentinamente, las causas más comunes son que Rovo se haya deshabilitado a nivel de organización, exista un problema temporal de aprovisionamiento o se hayan modificado permisos de acceso. Pide a un administrador que revise…
-
Welcome to the community @Dylan Sawchuk The MCP Server can access multiple Jira sites if the authenticated Atlassian account has access to those sites and the tools support specifying the target cloud/site context. BUT, there is currently limited documentation covering multi-site usage within a single Claude MCP…
-
@Radu Coravuyour logs show that Dynamic Client Registration succeeds, PKCE is configured correctly, and the authorization URL includes the required resource parameter. Since the same client worked for another Atlassian account and later began working for your account without any code changes, this points to a temporary…
-
I second that welcome @Ankith Nath This sounds like a tool-execution bug rather than a prompt issue. The confirmation dialog appears, so the agent is reaching the Update priority skill, but the confirmed action is not completing and the approval step loops. I’d test a second simple agent to confirm whether it is…
-
Hi @Jo-Lee Bertrand, your frustration is understandable. The bigger issue isn't that Rovo can't perform certain Confluence actions—it's that it sometimes reports success when no change was made or when the result isn't what was requested. Several community members have reported similar experiences with page editing, page…
-
Hey @Diem Chau, since the agent was created before the model/UI switch and the subagents disappeared after migration, this sounds like a Rovo Studio migration or UI regression rather than an instruction issue. If the agent still responds but subagents can’t be viewed or added, I’d open an Atlassian Support ticket and…
-
Welcome to the community @Chris_Payne! If the account is a Site Admin and has Admin or Collaborator access to the agent, then it should be able to add the agent to the help center. Since assigning Org Admin didn't resolve it, this may be a permissions sync issue or a backend defect. I'd recommend opening an Atlassian…
-
@Aditya Raman welcome to the community. Since both write and read-only tools return the same embedded error after MCP connects successfully, this looks less like a Jira payload or required-field issue and more like an MCP permission/backend execution problem. I’d first confirm Jira Read, Search, and Write are enabled under…
-
Welcome to the community @Astrid Vreugdenhil. We’re seeing similar reports from other Claude Enterprise users. If the connector is authenticated but resource search only shows confluence-widget-openai and jira-widget-openai, while URLs and search return no results, the issue appears to be in the Claude–Rovo integration…
-
Hi @Scott Moore, if re-authentication succeeds but Claude still reports Failed to reconnect to atlassian: -32000, the issue is likely with the MCP connection rather than Jira access itself. A few users have recently reported MCP authentication and connectivity issues despite successful authorization. I'd check whether the…
-
Welcome @pratap mutadak, as @Rebekka Heilmann _viadee_mentioned if Create Flow with Rovo disappeared from Jira Automation, first check whether Rovo is still available elsewhere in Jira (Chat with Rovo, Agents, etc.). Atlassian has been rolling out changes to Rovo, and some features may move or depend on site settings and…
-
@Greg Sypolt I second that welcome. This sounds more like a frontend entitlement or feature-flag synchronization issue than a browser problem, especially since multiple users are affected and refreshing eventually restores access. Capturing network traffic the next time it occurs is a good idea. Since you're part of the…
-
The great @John Funk Welcome to the community @Jacob Briggs. This sounds like a stale connector association rather than a configuration issue. If the SharePoint connector no longer appears under Rovo Connectors or Atlassian Administration but Resolution Management still reports linked folders, the remaining reference is…
-
@Viktor Makarevich /authv2 is for the OAuth 2.1/DCR authorization flow, not a drop-in replacement for the MCP server URL. Many clients should still connect to <a href="https://mcp.atlassian.com/v1/mcp" target="_blank" rel="nofollow noopener noreferrer">https://mcp.atlassian.com/v1/mcp</a> and let the MCP client/proxy…
-
@Warren Clark I second that welcome. An empty MCP response in production usually points to a difference between the local and deployed environment: auth method, enabled MCP permission groups, token/user permissions, gateway filtering, or network/proxy handling. I’d compare local vs. prod headers, token type, org MCP…
-
@Nick Hatch browser extensions, uBlock filters, or custom userscripts can hide Rovo UI elements locally, but I’d be careful with this approach. It may break when Atlassian changes the UI and could create security or support concerns, especially in managed environments. For org-wide control, the safer path is still…
-
@Ranvijay Singh what you're describing sounds less like a board configuration issue and more like a context-selection problem. Rovo does not currently have strong board-level awareness and often relies on chat history, project context, and recently selected objects. When multiple boards share the same Jira project, context…
-
@Kannan Chockalingam this is expected behavior today. I'd add Rovo can sometimes reference files such as CSVs, Markdown files, or HTML files under <span>/output/...</span>, but those paths are not generally accessible to users. If you need the data, ask Rovo to return it directly in the chat, split the results into smaller…
-
@Gabriel Zanetti the issue may be related to backend entitlement or site provisioning rather than configuration. Since support has resolved similar cases, opening a ticket is the right next step, especially when the error persists across different automation actors.
-
@Oren Koren Welcome to the community! This does not appear to be isolated. Another thread reports the same Claude + Rovo connector behavior: only confluence-widget-openai / jira-widget-openai appear, URL fetches fail, and search does not resolve resources. Since Claude’s Atlassian connector is meant to access Jira and…
-
@Ricardo Nóbrega welcome to the community. This usually points to the MCP client losing or changing the PKCE code_verifier between authorization and token exchange. Since Atlassian MCP Authv2 uses OAuth 2.1 with PKCE/DCR, the verifier must match the original challenge exactly. I’d test with a known supported MCP client or…
-
@Bobby Moyini today, this workflow has a gap. “Create with Rovo” can generate a page because it keeps a human review/publish step, but a Rovo Agent may not reliably publish a Confluence page on its own. Automation can create a page from {{agentResponse}}, but Rovo invoked through automation does not currently read…
-
@Nadia Volanovsky welcome! Rebekka’s answer is spot on. Evals are the current starting point for repeatable agent testing, but they only solve part of the problem. For scale, teams still need test sets, expected outputs, human review, and checks that actions actually happened—not just that the agent said they did. A Studio…
-
@richa bhatnagar welcome to the community. I would not rely on a Rovo Agent alone for exact sprint counts or estimates. Agents can summarize and reason over Jira data, but they may miscount or merge context unless the source data is constrained. For stakeholder views, use Jira reports, dashboards, JQL, or automation for…