Dr Valeri Colon (Connect Centric) Community Champion

Hi @張肇倫 and welcome to the community. RovoDev currently runs a background Git-AI stats check every ~30 seconds. This is built into the Atlassian VS Code extension and cannot be disabled from settings yet. Renaming git-ai.exe stops the popup but only until VS Code refreshes its workspace storage, as you’ve seen. The only…

Hi @Ramathirtha Randhi welcome to the community. Rovo’s semantic similarity isn’t deterministic, so suggestions can vary between runs. It doesn’t continuously “learn” from your Jira history, and it may rely on partial indexing or fall back to general reasoning when data isn’t available. You can improve accuracy by…

Hi @Phat Le Timeouts usually happen when a Forge-based Rovo agent runs an action that takes longer than the UI request window allows—complex test-case creation, large payloads, or slow app responses. Atlassian recently updated the agent UI and execution flow, which reduced these UI-level timeouts. The underlying issue…

Hi @Andrew Allen Rovo agents can comment on a page, but Jira/Confluence Automation can’t loop through pages and run a Rovo agent inside each branch. The “Lookup pages” action returns a list, but Rovo can only run once per rule, not once per item in a branch. Workarounds today:• Use “Lookup pages,” then pass the list of…

Welcome to the community @Puneet Upadhyay Rovo can create a sub-task, but the Create Work Item skill only works if the parent issue key is passed in the exact field the action expects. Rovo often misunderstands this unless your instructions are very explicit. Add guidance like: “When creating a sub-task, always set…

Hi @rushikesh.shivajishinde and welcome to the community. Semantic discovery isn’t built into Jira/Zephyr, so Rovo can’t natively “semantic-search BBIs.” The pattern that works today is: expose BBIs to Rovo as a knowledge source (Confluence pages or structured Forge data), then have your Forge app fetch relevant BBIs for a…

@Anthony Powell welcome to the community. The SharePoint connector may be slow at first, but no results after 24–48 hours usually means a permission or scope issue. The Graph app must have site-level read access and all required permissions granted by an admin. Indexing also works better when pointed to a specific site,…

Hi @大久保匡騎 welcome to the community. The @atlassian-rovo command only works if the Atlassian Rovo for GitHub Copilot extension is installed in VS Code and your GitHub org is linked to an Atlassian Cloud site that has Rovo enabled. Seeing “Atlassian” in GitHub app settings isn’t enough—Rovo won’t register in Copilot Chat…

現時点で、Atlassian Assist（Rovo/AI 機能）が断続的に利用できなくなる事象は一部の環境で報告されています。多くの場合、原因は一時的なバックエンド障害や負荷、または段階的ロールアウト中の不安定さによるものです。恒久的な停止や設定不備ではないケースが大半です。継続する場合は Atlassian Status の確認と、発生時刻を添えてサポートへ問い合わせることが推奨されています。

@Matt Riti This is a known behavior with the Create Work Item skill. The quick Create action doesn’t always persist rich Description content unless the agent explicitly maps the Description field in the action payload. When you click Edit details, Jira reopens the full create dialog and saves the field correctly. To fix…

Hi @Christopher Danner let me rephrase and add to what @Rebekka Heilmann _viadee_ is saying - This is usually a capability limit, not your config. Rovo can read issues and fields (including story points) but it doesn’t always have access to the agile report metrics (commit/add/remove/velocity) the way eazyBI does, because…

Hi @Dustin Alcock and @Artem Taranenko Yes, others have seen this. SharePoint indexing can take longer than 48 hours, especially for first-time syncs, and “Ongoing Sync” doesn’t surface detailed progress or errors yet. There are no admin-visible logs today. Common blockers include SharePoint permission inheritance,…

@Nina Dragušica welcome to the community - Parts of this are achievable today, with some limits. Rovo in JSM can analyze requests after submission to summarize, flag missing info, and suggest follow-up questions, but it can’t yet block or validate a request before creation on the portal. It also doesn’t “learn”…

@Kaspanoombro This usually happens because MCP session state is cached in more than one place (VS Code + the MCP extension + local storage), so you end up with a stale session ID after switching accounts, which triggers “Session not found”. Fixes that typically work: Use the correct endpoint: VS Code should point to <a…

Hi @Arun George welcome to the community- Today, Atlassian’s MCP server requires a browser-based OAuth sign-in for Jira actions (including linking issues). If VS Code prompts you to “move to the browser,” that’s the required auth step—you can’t link issues via MCP without completing it. If you need a non-browser flow, use…

Hi @Ashutosh Kaushik This usually happens when the request is interpreted as multiple actionable intents or when the client retries the same MCP action (for example due to timeouts or retries at the transport layer). MCP doesn’t currently guarantee idempotency for create-issue actions. Workarounds: add explicit wording…

I think this is common, @Aaron Lawrence after teams move past the AI discovery phase, they often start to overgeneralize what these tools can do. At that point, the focus shifts to helping people understand the boundaries and limitations, not just the possibilities.

We chatted about this in our Champion Slack. To add to @Tomislav Tobijas Not directly. Rovo works only with data it can already access inside Atlassian tools. To do brand monitoring, you’d need an external monitoring service (RSS, Google Alerts, social listening tools) and then feed the results into Jira or Confluence via…

Thanks for posting Support's official respone @Maor Levinas Shout out to a rising star @Bill Sheboy and my love always to @Rebekka Heilmann _viadee_ Yes—50 is a practical limit. Rovo agents in Automation don’t reliably handle large JQL result sets, so they cap what’s returned/processed. There’s no setting to raise it…

@Steve Rigby From Atlassian’s docs, the MCP tools generally work with Markdown/plain text payloads (they even call out Markdown bodies for Confluence). Today there’s no documented way to send raw ADF JSON through the Atlassian Rovo MCP tools, and the community has open requests to return/handle ADF for Jira fields. If you…

Oof — I get why that’s frustrating @Renaud Pagin. Today, end users can’t fully opt out of Rovo on their own. Rovo is enabled and governed at the site/org level, and there’s currently no global “disable for everyone” switch that removes all UI exposure once it’s on. Atlassian has acknowledged this gap (there is a feature…

@Peter M Yes—this can happen intermittently due to Rovo/Jira backend timeouts or automation context fetch failures (not your permissions), which is why an immediate retry can work. As a workaround, pass key fields into the prompt (summary/description) instead of only a URL, keep threads short, and add a retry/delay in the…

Hi @Cyril Joseph welcome to the community. No—Atlassian’s official Rovo Remote MCP Server (mcp.atlassian.com) currently authenticates via OAuth 2.1 (browser-based sign-in + scopes). It doesn’t support PAT/API tokens as a substitute for the OAuth flow, so a “headless” service-account PAT approach won’t work today.

現時点では、Rovoエージェントのナレッジソースとして直接「キュー内のJiraチケット」を指定することはできません。Rovoは主に Confluenceスペース（ページ・ナレッジベース） を知識源として参照します。Jira課題はリアルタイムの検索・要約対象にはなりますが、永続的な学習用ナレッジソースとしては扱われません。 回避策としては、 重要なチケット内容をConfluenceにまとめる エージェントの指示で「関連Jira課題を検索して要約する」と明示する といった方法が現実的です。

@johan_drabarek This is a known limitation. Rovo currently can’t be manually removed by org admins, and it can block org deletion. As you know, Atlassian has confirmed this behavior and is tracking fixes under AX-429 and ROVO-144. The only resolution today is manual removal by Atlassian Support. Please open a support…

Thanks @Ajay _view26_ I'll add that this isn’t a defect so much as a known limitation. Rovo is trained on a mix of historical and current documentation, and UI navigation changes roll out faster than training updates. There’s no published date for “version-aware” navigation responses yet. Best practice today is to ask Rovo…

@luke_twogood I'll add: Right now, Rovo agents can’t fetch or read Bitbucket file contents just from a URL, even if you have access. When it “works” in Confluence, it’s usually guessing based on the filename or context, not actually reading the file. Automations are stricter and surface the permission error instead of…

Thank @Oleksii Melnyk _MOY Apps_ I'd add... For the future, apply Rovo edits in smaller steps, manually save drafts, or use Live Docs, which auto-create versions and make recovery much easier. If Rovo edits are applied and saved and no page version exists, Confluence cannot restore overwritten content. Undo (Ctrl/Cmd + Z)…

That field isn’t a Jira “custom field” — it’s the Release/Version description (new rich-text “Section”). Today, the standard Versions REST endpoints still expose the legacy description string, but the rich-text section isn’t reliably writable/readable via REST yet, so Automation can’t target it directly. Track/request via…

@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…