Dr Valeri Colon (Connect Centric) Community Champion

@Syed Atif Hussain I'd add... This usually happens when the local STDIO MCP server process can’t launch reliably (path/permissions, missing deps, or the CLI/plugin version). Quick checks: update the Atlassian CLI/Rovo plugin to the latest, run the IDE/terminal as the same user that installed it, and verify the command path…

@Anuj Batta I would encourage you to take a class from Atlassian Learning to understand more about Rovo. But to respond to your post: You can do this with one agent that asks 2 questions first: “Which team?” and “Which meeting: Forecast / Retro / Daily?” Then it filters issues using your team signal (labels/components/team…

@Vladislav Popov a 524 from mcp.atlassian.com points to a service timeout/outage, so yes—this can be “normal” during an incident and it will block tool discovery before Jira perms are even checked. Reconnect the app, confirm your org allows the ChatGPT connector (allowlist/governance), then retry. If it persists, capture…

@mahesh_komirishetti add to this: the “3LO token that works for api.atlassian.com” can still fail for MCP because MCP expects an OAuth 2.1 token issued for the MCP resource/audience via the MCP auth flow (PKCE)—not a reused REST API bearer token, which leads to invalid_token. Also, /v1/ is not a JSON-RPC base URL; connect…

@Ram Mehta I'll add...that error usually means session.call_tool() is raising/returning a string error payload, and your client code (or the MCP lib) expects an object with a .message field (what @Tomislav Tobijas mentioned). Common causes: wrong argument shape, tool name mismatch, or server returning a plain-text error.…

@Anuj Batta Rovo agents don’t currently run directly against a specific board. They work at the project/issue level. To scope results, update your agent instructions to ask which team/board to use and then filter by board-related signals like Sprint name, board filter JQL, labels, components, or team field. Example: “If…

@Dor Blayzer @Clark Everson This usually happens because Rovo agents often don’t auto-run write actions on the first message—they’ll draft the content, then wait for a clear “go ahead” to create/update items. That’s why you see actionIds configured but actions: [] empty. Fix: adjust the prompt/instructions to include an…

@Vladislav Popov This isn’t a permissions issue—you’re right. Atlassian Rovo is designed UI-first, and direct Jira/Confluence API access from ChatGPT is not guaranteed or supported long-term. The MCP connector relies on the Atlassian MCP gateway; if mcp.atlassian.com (SSE) is unavailable, discovery fails and no actions can…

Thanks @Tomislav Tobijas and @Shakeel Bhamani I'll add, yes—this is a known limitation today. updateConfluencePage typically updates content in a simplified format, so rich Confluence macros (like /status) can get “flattened” into plain text. Workarounds: avoid rewriting the whole page, or update using Confluence storage…

@Adam Tumidalski Likely cause: auth method + permissions mismatch. Atlassian’s remote MCP server uses OAuth, not Jira API tokens, and actions run with the user’s Jira permissions. So a 401/“no permission to create issue” usually means the client isn’t completing OAuth, the wrong site is connected, or the user lacks Create…

I'll add to this with the link to the Jira board for Rovo feature requests... https://jira.atlassian.com/projects/ROVO/issues/ROVO-239?filter=allopenissues 

Hi @Nachiyar.M in response to your initial question: Yes—this behavior is expected unless the agent is explicitly constrained. Rovo agents don’t automatically quote documents step-by-step; they summarize or rephrase based on understanding. If the instructions allow flexibility, the agent may share links or inferred steps…

I'll add to this @manikanta_ambati_accenture to say, this is usually a proxy/session-handling issue. Atlassian MCP’s OAuth flow relies on a browser session + redirect back to <a href="http://localhost:3334/" target="_blank" rel="nofollow noopener noreferrer">http://localhost:3334/</a>..., and Atlassian notes corporate…

@Manoj Prabhakar Battula and @Uladzimir_Pauliukovich When Rovo agents show a “network error,” it’s usually related to a temporary service disruption or backend timeout. Very long chat threads or large amounts of context can sometimes cause timeouts and show up as a “network error,” especially with custom Rovo agents. This…

I'll add to @Tomislav Tobijas response to say: Atlassian made Rovo available to all paid Cloud subscriptions (Standard, Premium, Enterprise) at no additional cost. However, capabilities still vary by plan. Standard users get core Rovo Search and Chat, while Rovo Studio (custom agents), advanced governance, and some…

Thanks for the link @Brant Schroeder I'll add that currently Rovo doesn’t have a standalone mobile app to install. To use Rovo on your phone, install the Jira or Confluence mobile app from the iOS App Store or Google Play, sign in to your Atlassian Cloud account, and access Rovo features from within those apps (like…

@Nitisha Paresay Rovo can only create an issue type if every field marked as required on that issue type’s Create screen is provided at creation time. For Stories, this usually includes Summary plus any required custom fields your project enforces (such as Priority, Components, or team-specific fields). For Epics, an Epic…

Your workaround makes perfect sense given the scope. When it’s just a few IDs, adding them manually is way more efficient than setting up a full API call. That kind of practical thinking is what makes real-world use cases so valuable. And yes — Rovo having more awareness of Jira’s technical elements like custom field and…

Every month (or quarter, depending on how busy things get), I do a full review of the Rovo Q&A forum to keep it helpful, accurate, and organized: I read every question that’s been posted. Yes, all of them. For questions with accepted answers, I double-check for accuracy. For those without accepted answers, I mark the first…

But you brought new meaning to it @Alex Ortiz 

Thank you, @Rebekka Heilmann _viadee_ ! That means a lot to me ❤️ Honestly, these reviews wouldn’t be possible without you and the others jumping in to answer questions in real time. Your contributions save me hours (and at times days) and make it so much easier to surface common themes. I’m really glad to hear the…

You’re very welcome @Don Hames — and I completely get where you’re coming from. It’s frustrating when something that feels like a basic, expected functionality just isn’t there yet. Clearer communication around current limitations would’ve saved a lot of time and energy — especially for those of us actively building and…

@Darryl Lee I smile every time I see your avatar — you’re an unsung hero in this space. Product communities can sometimes get so caught up in positivity that they lose a bit of authenticity. When we ignore the problems, we stop solving them. Your “protagonist energy” is constructive and rooted in care — it’s clear you’re…

@Anuj Batta You don’t need code, but you do need to design around how Rovo scopes context. Rovo agents don’t attach to boards directly; they work from Jira issues and Confluence content. To make a generic Sprint Retrospective agent usable across multiple boards, have it ask which board or sprint to analyze at runtime. Use…

@Martin Poirier This is a fair concern, and you’re not alone—Rovo’s current credit model is still maturing for large enterprises. To add to @Rebekka Heilmann _viadee_ point, today Rovo is best suited for targeted, high-value use cases, not broad “AI everywhere” rollout. Automations, deep analysis, and large-batch queries…

@Gabriel Viger This is less about JQL syntax and more about how Rovo handles reasoning and formatting together. While Rovo reliably retrieves JQL results, it becomes inconsistent when it has to sort, interpret, translate, and render a table in one pass. The most reliable approach is to make the JQL the single source of…

@Valentin It is a shame. @Jack Brickey 's Technical Support option= Account & billing → Organizations, explicitly stating you need Rovo removed to delete an unused org. 

t.pfaff@foodtracks.de Even when you add a page as agent knowledge, Rovo won’t always pull it into every answer. It first decides whether that content is relevant, and if the question is broad it may answer from general knowledge instead. Two fixes usually help: (1) make your prompt explicitly point to the source, e.g. “Use…

@Huang Ke Bin 感谢你分享截图——这不是你的操作问题，而且你并不孤单。我是截图2里那位 Valeri。由于监管要求、基础设施调整以及区域服务可用性等原因，Atlassian Cloud 在中国大陆用户创建站点（site）时，确实会出现间歇性不可用或被阻断的情况。出现这种情况时，账号可以正常注册，但站点开通/配置（provisioning）会失败，导致 Jira、Confluence、Rovo 等产品都无法使用。很遗憾这是平台层面的限制，不是你本地能修复的。 目前相对可行的办法是：提交 Atlassian Support 工单并注明“在中国大陆无法创建站点”的问题；或尝试在中国大陆以外的网络环境/地区（例如…

@Ash McConnell This is a known limitation of Rovo Dev’s command-approval model. Each dynamically generated bash command is treated as a separate execution, so when Rovo writes files line by line (for example using repeated cat or heredocs), it triggers a permission prompt for every variation—even if you select “Allow…