Dr Valeri Colon (Connect Centric) Community Champion

@David Sanchez I'd add, Atlassian states the Rovo MCP server does not store or cache Jira or Confluence content; it acts as a secure proxy. I’d test in a fresh Claude chat and ask it to return the issue’s updated timestamp and latest comment timestamp. If those are still stale, reconnect the Atlassian integration and open…

@May Rosales your testing is valuable because it demonstrates the model can produce the correct 7-column output but is not consistently applying the instruction after migration. The fact that the formatting works more reliably when placed in the Trigger field suggests instruction prioritization may have changed between the…

@Dennis Harter SharePoint support has not been removed from Rovo. Atlassian recently updated the SharePoint connector authentication model and existing SharePoint connectors may require admin reauthorization and updated Microsoft consent. Atlassian warns that connectors not refreshed can stop syncing and Rovo may rely on…

@Yuvie Naidoo welcome! This is a strong enterprise use case. Bulk import/export, versioning, and API-based management would make Rovo Studio much easier to govern across environments. For now, agent and sub-agent setup is still UI-driven, and switching the model only changes the LLM used by the agent, not the Studio build…

@mispr if this behavior started recently across existing repositories and there is no corresponding repository, workspace, pipeline, or automation configuration, it may be a new Rovo Dev feature rollout or a product defect. The <span>.rovodev/.review-agent.md</span> file is used to customize review behavior, but there…

@Brendan Dwan I'd add, today, the best approach is still to document key Assets configuration in Confluence and let Rovo use that documentation as a knowledge source. Rovo can help answer questions about documented configurations, but it cannot reliably discover or explain detailed Assets schema settings directly from the…

Welcome @Suryanarayanan Sayee Subramanian! Today, Rovo Agents can help generate content and visualizations, but they don't reliably create and configure Jira Chart macros with JQL queries on Confluence pages. If you need a live Created vs Resolved chart, the most dependable approach is still to add the Jira macro manually…

@Richard Chen and @Yuvie Naidoo welcome! The fact that the agent works in Studio, Slack recognizes the trigger and another customer reports the same behavior during the same timeframe suggests the issue is likely in the Slack-to-Rovo execution pipeline rather than the agent configuration itself. Since the trigger is…

@Antun Modrušan welcome to the community. This sounds like the right path. Since it works intermittently, I’d compare successful vs. failed PRs by author, repo, branch size, Jira context, and timestamp. If a one-line PR still fails after toggling reviews off/on, it’s likely something Atlassian needs to inspect from backend…

@Mario I'd add that for the questionnaire use case, I’d separate “answer drafting” from “form submission.” Rovo can use Google Sheets as a knowledge source to find and draft answers, but writing back to a form or spreadsheet usually requires a custom skill, MCP server, API, or automation tool. I’d keep Rovo as the…

@Maximilian Seifert since you’re the org/site admin, have one site, and already enabled the MCP settings, this sounds less like normal user approval and more like the app itself is not approved under 'Connected apps' or the redirect/client registration is mismatched. I’d reauthorize from a clean session, confirm the exact…

@Maybe Gil I second that welcome. What you're seeing is likely related to Jira attachment authentication rather than image detection. Rovo can often identify attachment metadata and content, but attachment URLs typically require the viewer to be authenticated and have permission to the Jira issue. As a result, a URL…

@Marcos Pino Flores I agree with Martin here. For bulk user/account creation from a spreadsheet, Jira Automation alone may not be enough, and Rovo is not the most reliable option for parsing Excel rows and sending structured emails per row. A better path would be ScriptRunner, Assets, or an external automation/API flow…

@Daniel ABDULAZIZ for fully unattended automation, Jira Automation or API may still be better. Rovo is strongest when a user or agent-guided workflow reviews/acts on the story content before creating tickets.

Welcome to the community @Muhammed U KThe MCP OAuth token is for the Rovo MCP server, not a standard Atlassian REST API token, so /me and /accessible-resources may return 401 even when MCP tools work. Today, account/user lookup does not appear to be exposed through MCP auth. The practical workaround is to capture the…

Welcome to the community @Jerome Grunnagle _Trey_ and @Ivan Rener @Ben Johnson based on current Atlassian documentation, pre-registered OAuth 2.0 apps are supported; DCR is recommended but not required. Since the MCP server accepts the token and returns the tool list, this doesn't appear to be a licensing issue. Atlassian…

@Venkatesh Soundararajan this likely comes down to Xray-managed required/custom fields. Rovo’s Jira creation skill can create standard Jira work items, but third-party issue types with app-managed fields may not be fully supported, especially if fields like Test Type or Test Steps are required. I’d test creating a basic…

@Ben Johnson If this still occurs after 24 hours, I would stop treating it as a transient outage. An "Internal Server Error" during MCP authentication is usually occurring in the OAuth or authorization flow rather than the MCP client itself. I'd try an incognito browser session, verify you're logged into the correct…

You're welcome @Jan 

@Lqsti Basti and @Daniel Jefferson welcome to the community. Since this post was opened, we've seen additional reports of similar behavior where some models remain unavailable despite an active Rovo Dev subscription and available credits. If GPT-5 and Haiku 4.5 work but Sonnet 4.5 and other models consistently return…

@Nikolai Ivanov native Confluence tables are generally the safest and most reliable option because they're part of the page content Rovo indexes. One thing I'd add is that table size and structure matter. Smaller, well-labeled tables tend to produce better results than very large or complex ones. If the data comes from…

Hi @Andrea Daniels since April, we've seen multiple reports very similar to your screenshot ("Model not available for current subscription" repeatedly falling back despite a paid plan), which suggests the service is failing to recognize the paid model entitlement even though the subscription exists This isn't something the…

@Dang Quang I think that’s a very pragmatic approach for the current state of Rovo. If the KB is fragmented, using the portal agent first as an intake/triage layer to collect structured information can help generate better future knowledge content over time. I’d just keep expectations focused on guided intake +…

Many thanks @Susan Hauth _Jira Queen_ for catching the discrepancy between the Zendesk documentation and actual functionality as well as connecting with the Rovo dev team to advocate for more functionality.

Some of the best ideas comes from those duckie threads. e.g. Founders Keynote Bingo 

I'm glad to know its helpful @Josh -- motivation to keep them going.

@Tom Haapanen what you’re seeing is real, and others are hitting it too. Rovo can create Confluence pages, but page creation from chat is still inconsistent—especially around parent placement, persistence, and verification/search indexing. The most reliable patterns today are: Create with Rovo from the editor Use Rovo for…

@Jan totally hear your frustration. Even with a resolved parent (link/ID), child page placement from chat isn’t consistently reliable yet. That’s a current limitation, not a configuration issue. What’s working more reliably today: Use Automation (Confluence/Jira) to create the page with the correct parent Let Rovo handle…

@Bernardo Silva go to https://support.atlassian.com/contact 

@Kinaba Anazo sorry you’re experiencing this as well—that’s definitely frustrating. This is typically an entitlement sync or backend delay, especially right after purchase. I’d double check that the plan is fully active (not still in trial), that users are assigned to Rovo Dev, and try logging out/in of the CLI. If it’s…