Dr Valeri Colon (Connect Centric) Community Champion

@植木　智子 さん、こんにちは。 ご説明を見る限り、通常のRovo Chatでは同じ指示でコンテキストが保持され、「会話のきっかけ」から実行した場合だけコンテキストが削除される、という状況でしょうか。 「会話のきっかけ」はエージェントを開始するための**提案プロンプト（質問・指示）**として設計されています。エージェントが毎回必ず参照すべき定型指示であれば、「会話のきっかけ」ではなく、Agentの Behavior / Instructions 側に設定する方が適しています。Atlassianのドキュメントでも、Conversation StartersとAgent Instructionsは別の設定として扱われています。…

@Dorota Kmiecik welcome to the community. Your setup looks consistent with Atlassian’s documented smart values—{{agentResponse}} should contain the agent reply, and {{agentResponse.asString}} is useful for plain-text conditions. Since the audit log shows the response itself is missing, this matches ROVO-288/ROVO-852 more…

@Jordy Jorissen based on your testing, I agree this is worth treating as a defect rather than continuing to troubleshoot individual chart configurations. The detail that stands out is that the preview is wrong, but selecting it opens the correct chart. Combined with different users seeing different incorrect previews and…

@Alejandro Álvarez since Jira works for these users but Confluence returns 403, I’d compare their OAuth consent rather than just Atlassian groups. Rovo MCP enforces product-specific scopes and permissions per user. Have one affected user revoke the Claude/Atlassian connection under Connected apps, reconnect, and confirm…

@심제범 _jbsim0413_ this looks like the same Atlassian-side OAuth scope mismatch others reported on July 8. The *:townsquare Goals/Projects scopes have a known availability gap (ECO-1420), so I wouldn’t try to fix this in Claude. Since the built-in Rovo MCP connection itself is requesting scopes Atlassian then rejects, I’d…

@jackson gnanasekaran welcome to the community. I think your interpretation is on the right track. Atlassian already has ECO-1420 tracking the fact that the older *:townsquare Goals/Projects scopes aren't exposed through OAuth apps, Forge, or scoped API tokens. If the Rovo MCP OAuth flow itself is requesting…

@Shih Ting Yeh _RD-TW_ welcome to the community. One useful clarification: getConfluencePage retrieves a page by ID; it isn’t a search tool. If multiple parallel calls are returning the same page, I’d verify that each call is actually receiving a different pageId. For different query conditions, use…

@Sarah Miracle welcome to the community. I checked the current Rovo Slack documentation, and I think you’ve found a documentation gap or possibly an incomplete feature. Atlassian documents searching for agents from the Slack Home tab, but I can’t find documentation showing where an agent selected with … > Bookmark should…

@Kumarprem Gade Welcome to the community. If you want the RCA for the ticket you’re currently viewing, make that context explicit: “Using only this work item and its related comments/history, generate a root cause analysis.” Rovo Chat can use the current Jira work item as context, but vague prompts may pull broader…

@Vasco your debug output shows the agent is returning a JSON object, so {{agentResponse.comment}} won’t parse that nested value. Ask the agent to return valid JSON only, then use {{agentResponse.asObject.comment}} in Add comment. If you don’t need structured JSON, simplify the prompt so the agent returns only the comment…

@OHNISHI Katsuya_Ricksoft_ welcome to the community. Since a new Studio app still works, I’d focus on the affected app rather than your browser. Check the Forge logs/deployment status for that app and compare them with a working one. If the agent returns literally no response and nothing changed on your side, capture the…

@Tom Polten _RCS_ welcome to the community. Update: ChatGPT Workspace Agents now officially support adding custom MCPs in Agent Builder on Business and Enterprise/Edu. So Rovo doesn’t need to appear in the native app catalog—you can add Atlassian Rovo directly as a custom MCP tool using <a…

@Krishna Modem I’d troubleshoot this as a retrieval/configuration issue rather than trying to solve it through stronger prompt instructions. First, start a new chat to eliminate previous conversation context. Then verify the agent’s current Knowledge configuration and Instructions to make sure the old page, URL, or content…

@Andrea Del Pilar Porras Rodríguez welcome to the community. One clarification based on the current Rovo Chat controls: users can now filter company knowledge by specific Atlassian or connected third-party apps from Chat’s Sources settings. However, this is app-level filtering rather than an enforced boundary for…

One update for anyone finding this later: Atlassian’s current documentation actually recommends <a href="https://mcp.atlassian.com/v1/mcp/authv2" target="_blank" rel="nofollow noopener noreferrer">https://mcp.atlassian.com/v1/mcp/authv2</a> for OAuth 2.1 clients. /v1/sse is definitely retired, but /authv2 itself isn’t…

@Kristian Kaa welcome to the community. One thing worth clarifying: this isn’t something you can currently fix by refining the agent instructions. Rovo can create the Jira work item, but passing a file uploaded in Chat into the new work item as an attachment isn’t currently a supported action. That’s why the agent can say…

@Jeffrey Bistrong Rebekka has the right approach. Studio routes these automations into the selected app/space, but Jira Automation supports app-level/global rules. I’d create the rule globally, then use conditions to limit execution to the desired project category before invoking the Rovo agent. Just put those filters as…

@Mau Jimenez one clarification for Premium: Atlassian currently documents Rovo access controls at the app level, while group-based allow/block controls are an Enterprise capability. I wouldn’t use IP allowlisting as a long-term workaround for credit management since that’s a security control rather than a usage control.…

@Bhargav Karanam welcome to the community. You’re right that /v1/authorize is part of the browser-facing OAuth flow; a valid request should not consistently return HTTP 500. Atlassian had just migrated Rovo MCP to a new DCR OAuth provider, so stale client registration/metadata or a transient backend issue is plausible.…

@Toura Nobles unfortunately, if you’re referring to Jira’s newer work-item preview panel, you haven’t missed a setting. There currently isn’t a user or admin toggle that restores the previous click behavior in the affected views. You can still open the full work item from the preview, but permanently disabling the panel…

@Jan Karczewicz welcome to the community. There’s an important distinction between data residency and AI processing location. Rovo supports EU data residency for eligible stored data, but that doesn’t guarantee all Rovo processing remains within the EEA. Atlassian currently lists AI subprocessors with processing locations…

@Srinivas_ Chaitra _Agoda_ welcome to the community. This error actually suggests Cursor reached Atlassian successfully, but the Atlassian account completing OAuth isn’t being matched to an eligible Jira, Confluence, or Compass Cloud site. I’d first verify you’re authenticating with the correct Atlassian account and that…

@Anandhi Arumugam _Cprime_ One distinction may help your investigation: prompt injection or sensitive-data disclosure doesn’t necessarily point to the underlying LLM. Rovo retrieves authorized organizational data and can use tools/actions around the model, so findings can occur in retrieval, context handling, tool…

@dbonvill welcome to the community. Alexander’s cleanup approach makes sense here. Atlassian confirms Rovo Dev can update independently of ACLI, so the failure is occurring during that plugin update rather than normal Rovo authentication. Since the existing rovodev directory appears to be blocking the replacement, removing…

@Vadym Chu welcome to the community. Since the 403 is coming from Rovo’s eligibility check and your blocklist/configuration hasn’t changed, I’d avoid chasing local fixes too far. IP allowlists can affect Rovo/MCP access, but if the required ranges are already allowed and the failure affects Rovo Chat itself, Atlassian…

@Nhat Trung Vo your later finding is the important update: ROVO-870 confirms that standard Developer Console 3LO OAuth clients aren’t currently supported as static OAuth clients for Remote MCP. Interactive custom clients need to use Rovo MCP’s OAuth 2.1/DCR flow; for backend/M2M integrations, API-token or service-account…

@AZamorano glad the explicit prompt worked. One clarification: I wouldn’t assume your original prompt was necessarily wrong. The Rovo ChatGPT integration retrieves Jira through Atlassian’s MCP/API layer, and Atlassian has already fixed a related connector bug involving incorrect Jira URLs. Asking specifically for the…

@Eric J Trumbull this is an important distinction. Atlassian’s current documentation says admin-managed connectors listen for source deletions and update the Rovo index, but Support has apparently confirmed that Teams retention-policy deletion isn’t treated the same as user deletion. That’s a meaningful governance gap for…

@Kamlesh Panchal I’d first check Studio → Agent → Surfaces → Help center and confirm X is actually enabled for that help center. Atlassian allows only one Rovo agent to be displayed there at a time, so Y may be the agent currently assigned to that surface. If Studio shows X assigned but the portal still displays Y, a…

@Jagruti Shinde a “Failed” result doesn’t necessarily mean the agent response itself is wrong. If you’re using Response Accuracy, an LLM judge compares the response against the expected answer in your CSV. Open a failed case and check the judge’s reasoning. I’d also run the same dataset using Manual Testing, which removes…