Dr Valeri Colon (Connect Centric) Community Champion

@Dave Mathijs wait, what?! Did Atlassian help find them? I suspect the model misinterpreted the intent and mapped it to the wrong action and/or the UI did not clearly communicate what that action actually was, Read Darryl's experience here. @Rebekka Heilmann _viadee_ things change so quickly with Rovo, thank you for the…

@Yong Yang these are beautiful. They're going to make an awesome Linkedin post.

Thanks @Josh always good to hear from you! Love that @Yong Yang wish I knew more than 3 words in Chinese so I could read how it turned out 

Thanks @Thomas Henney — that helps confirm this is reproducible and the screenshots were helpful as well @Rojahn Ahmadi . Since <span>links:read</span> isn’t showing in the published permission list but Slack blocks the install for that scope, this looks less like workspace configuration and more like a mismatch in the…

We should mention that Atlassian states contributed data is used to improve Rovo and Atlassian Intelligence—not for advertising or marketing, and not shared with or used to train third-party foundation models (like OpenAI or Anthropic). They also state they de-identify contributed data where possible before using it for AI…

At this point @Rojahn Ahmadi I’d recommend opening an Atlassian support ticket and including the exact error, screenshots, and your Slack workspace type (Enterprise Grid vs. standalone workspace). This looks like something Atlassian’s Rovo team will likely need to investigate. I’d also be interested to hear if anyone else…

Welcome to the community @Rojahn Ahmadi This error is typically caused by Slack's app approval policies rather than a Rovo configuration issue. The links:read permission is a Slack scope that some organizations restrict through app governance or admin approval workflows. Verify in Slack Admin → App Management whether…

Thanks for sharing your findings, @Richa Goyal its helpful to know. One additional thing worth noting is that several MCP-related discussions over the past few weeks have involved authentication, OAuth metadata, dynamic client registration, and grant-type behavior. In a number of cases, tool discovery succeeded while…

You're welcome @Venkateswar Kasa. Since the issue is intermittent, try to determine whether the data is missing or whether the UI is failing to render it. A few things to check: Compare Forge logs from a successful run and an empty-card run Verify whether the payload contains the expected values when the card renders empty…

@pankaj pipada @I notified Atlassian on your behalf and support engineer will be in touch within 2 days.

@Jonghwan Choi welcome to the community. Yes, Rovo was down yesterday. I should be working today although many reported a circuit break error earlier.

@Arkadiusz Wroblewski you were there!? Had I seen I would've taken a moment to celebrate you taking #1 on the Rovo Q&A leaderboard. Its no small feat, Rebekka has held the position for months. I learn new AI tips and tricks from the community all the time. I'm glad the analogies landed, I was making them up as I went.

@Arkadiusz Wroblewski you rang ;) I haven't found any documentation indicating that rovo:agent manifest fields currently support Forge i18n resources. The validation error suggests the schema still expects literal strings. As a workaround, some developers create multilingual conversation starters (e.g., English/Korean in…

That's good context that will undoubtedly help others. Thanks @Ankith Nath 

Cheers!

Welcome to the community @Esteban Malano _Appricity_ Here's a related post Can Rovo Analyze Images in Confluence? [Champion Slack Insider]

@Sathwik Kumar I'd keep an eye on Atlassian's Rovo pricing and usage documentation, as allowances and overage policies may evolve over time. Thanks @Jason Krewson

Hi @Venkatesh Parthiban_G. @Bill Sheboy is right that Support is the best path for the exact failure reason because the public automation audit log may not expose Rovo’s internal timeout, context, or parsing errors. As a workaround, I’d simplify the rule: reduce the Lookup work items JQL, pass fewer fields, remove complex…

Welcome to the community @Adriaan Dippenaar It seems you're not alone—there are already requests for more detailed and real-time Rovo usage visibility. At the moment, admins can monitor overall Rovo usage and credit consumption through Atlassian Administration Insights and Platform Usage dashboards. However, I haven't seen…

@Ricardo Mendes @Pablo Herrera @Matthew Woolley @nick_strickland welcome all! Glad to have you here. Since multiple users are seeing this and old grants still work while new OAuth grants fail, this looks like a platform-side MCP/OAuth regression rather than a local credential/cache issue. Atlassian’s MCP docs point users…

@Venkateswar Kasa this sounds like an intermittent Forge rendering/state issue rather than expected behavior. I’d check whether the card is rendering before the generated data is available, especially if values are loaded async. Add loading/empty states, log the payload passed into the confirmation card, and confirm…

@Mikael Duong welcome to the community. Atlassian MCP currently appears to use the standard Jira comment API, which doesn’t create true JSM internal notes. Internal notes require the JSM Service Desk API with public: false. Until MCP supports that parameter/endpoint, the safer workaround is to have Claude draft the note,…

Welcome to the community @pankaj pipada Yes, this looks like a valid issue. Atlassian MCP supports OAuth 2.1/DCR, but RFC 8414 requires the metadata issuer to match the issuer URL exactly. Since strict clients reject the mismatch before consent, I’d raise this with Atlassian Support and include the curl outputs, trace ID,…

Welcome to the community @Kamil Leszczynski Image understanding in Rovo Chat is a supported capability, and Rovo can analyze uploaded images and extract text from screenshots. Since you're seeing intermittent success and the behavior changed recently while PDFs continue to work, this sounds more like a regression or…

@Shaked Cohen welcome to the community. If the MCP search tool is returning "Access denied: Your organization admin has not authorized the Search permission", then @Germán Morales 's explanation is likely the root cause and the Rovo MCP Server permissions should be reviewed by an org admin. But, if the tool is returning…

Welcome to the Community, @alvaro_lopez One thing worth checking is whether the relationships you're creating are actually among the Teamwork Graph "Supported relationship types." Atlassian's documentation currently lists a limited set of association combinations that are guaranteed to create traversable relationships in…

Hi @Arsenia Cabrera Based on the error message ("Invalid context provided. Please try authorizing again"), this appears to occur during the Atlassian authorization flow rather than during MCP tool execution. Since the Atlassian Rovo connector in Claude uses Atlassian-managed OAuth, and another user has reported similar…

Welcome to the Community, @Akash Jha. What you're describing goes beyond normal summarization drift. If the agent is introducing commands, thresholds, or remediation steps that don't exist on the source page, that's a grounding issue rather than a simple prompt issue. Prompts can reduce this risk, but there is currently no…

Welcome @Kristiyan Milanov based on your screenshots and follow-up, this may be more than a consent or permission issue. There have been several reports across the forum where Rovo reports that an action completed successfully, but the underlying action was never actually executed or persisted. While most reported cases…

Hi @Richa Goyal. Tool discovery working does not always mean tool execution is authorized. The error often appears when MCP connects but the requested action is blocked by permissions, scopes, auth method, or the site’s Rovo MCP settings. Also, MCP uses JSON-RPC rather than normal REST calls, so Postman must send the exact…