Dr Valeri Colon (Connect Centric) Community Champion

@zhiru cao Thanks for posting the resolution. Since the same VM worked with your colleague’s account and clearing %APPDATA%\Code\User\workspaceStorage for Atlascode restored Rovo Dev, this appears to have been stale/corrupted local VS Code extension state rather than Rovo Dev availability or your usage credits. For others…

@Paul Barrett welcome to the community. Since Apps → Connectors is missing entirely, this looks more like an org/site provisioning or eligibility issue than a specific connector problem. Atlassian requires an Org Admin on a verified business domain to enable Rovo and manage Teamwork Graph connectors. Verify the domain,…

@Scott Melhop welcome to the community. This isn’t currently supported natively by the Rovo MCP server. Atlassian is tracking file uploads to Confluence/Jira via MCP under ECO-1361. ECO-1265, mentioned above, is specifically for attachment downloads. Confluence’s REST API does support uploading attachments, so a custom…

@Jeremy Attard welcome to the community. Your testing suggests the connector itself is working because Rovo can retrieve the SharePoint file. I wouldn’t assume the empty filter is a connector problem. Atlassian’s current agent documentation clearly describes deeper scoping for Confluence, Jira and JSM, but doesn’t clearly…

A July 28 follow-up suggests the issue was subsequently resolved or mitigated. If you still sees it, recreating/reloading the action and then contacting Atlassian Support would be appropriate.

@Yudhees Two separate issues may be getting mixed together. Persistent memory is currently documented for Rovo Dev CLI via AGENTS.md; telling a custom Studio agent to “remember this” doesn’t guarantee cross-session persistence. For PR creation, Bitbucket supports a bitbucketPullRequest.create write tool with the required…

@Escobar_ Andy welcome to the community. I’d separate the calculation from the AI. Rovo can vary on large analytical requests, and Atlassian tracks silent failures for bulky agent workloads under ROVO-615. Use Jira Automation/JQL to calculate the sprint metrics, then pass the verified numbers to Rovo for interpretation and…

@Allen Dumler This is a valid governance gap. Current Rovo controls support instructions for individual agents, but I can’t find a documented organization-wide instruction/policy layer for default Rovo Chat. Guard Premium’s upcoming Rovo Chat security can block/redact detected sensitive data, but that differs from…

One small caveat: committed-vs-completed analysis depends on having the right historical sprint data available; Rovo shouldn’t be treated as the source of truth for deterministic metrics.

I'd just add saying there is “no allow/deny list” may be too broad. You can control available tools by configuring which tools each subagent has.

@Chris Green you may be hitting a context limit, but the agent instructions alone may not be the cause. A quarterly RCA can accumulate Jira results, comments, history, and tool output. Try smaller time periods in fresh chats and compare results. For larger analyses, split the work by period/category or use subagents, then…

@Kintur Shah since your org admin gets “Something went wrong” directly on the Rovo MCP Authentication setting across browsers/incognito, I wouldn’t keep treating this as a browser issue. Atlassian documents API-token authentication as an org-admin-controlled setting. If it can’t be enabled, OAuth 2.1 is the supported…

@Alvaro Aparicio I think you identified the adoption issue in your follow-up: availability and adoption are two different things. I’ve had better results treating AI adoption as a progression rather than a launch. Start with a controlled group and a specific workflow where success can be measured. Give users guidance on…

@Santanu Roy welcome to the community. Jira does support Create with Rovo from the Releases page, and saved release notes can appear under Related work. But I don’t see a documented native Rovo Agent skill that executes that full release-note workflow autonomously. The built-in Release Notes Drafter drafts notes; for…

@Vivian Erklavec Zajec Arek’s distinction is the key one: Rovo can generate the note text, but a functional Confluence @mention is a structured user reference, not just an @name string or guessed ADF. I’d avoid asking the agent to manufacture mention markup. Generate the notes first, then add people with Confluence’s…

For anyone finding this later: this was a bug, not intended conversation-starter behavior, and Daniel confirmed it was fixed after July 20. Atlassian’s current documentation says that when an agent is invoked from Jira or Confluence content, you can enter a prompt or select a conversation starter and the agent should…

@Hardik Babbar since JQL works, Rovo Search works through ChatGPT, and your whole org gets the 403 only in Claude, I’d treat this as a Claude/Rovo MCP path issue rather than normal Jira/Confluence permissions. Atlassian logs every MCP tool invocation, so ask Support to compare a failed Claude search call with a successful…

@Milena Esther de Sá welcome to the community. The safest conclusion is that sprint state changes aren’t a documented native Rovo Agent skill or Jira Automation action today. Since moving issues between sprints still works, I’d separate that from starting/completing the sprint itself. For a reliable workflow, handle sprint…

@AGASTYA SHARMA I’d separate prompting from a built-in safeguard. You can instruct a custom Rovo Agent to abstain when its sources don’t support an answer, but Atlassian doesn’t currently document an organization-wide knowledge-quality threshold that guarantees this behavior. A useful governance feature would be…

@AGASTYA SHARMA Martin’s example is a good proof point. Rovo can already identify knowledge gaps in JSM based on request patterns. The broader vision—finding duplicate knowledge, stale ownership, isolated teams, or undocumented processes across the whole organization—isn’t a documented general capability yet, but Teamwork…

@AGASTYA SHARMA I agree with Martin. I’d be cautious about asking the model to explain why it rejected every alternative source, because that explanation may itself be generated rather than a faithful record of retrieval. Rovo already exposes used sources, and Agent Debug can show tools/subagents involved. A more useful…

@AGASTYA SHARMA you can already configure this behavior in a custom Agent—for example, instruct it to challenge assumptions, identify conflicts with Jira/Confluence evidence, and clearly flag missing information. I’d put that in the Agent’s Behavior/Instructions rather than Memory, since Memory is personal to each user. So…

@AGASTYA SHARMA Rebekka’s right—Rovo now supports persistent memory across chats. The interesting governance question is less “should it remember?” and more what it should remember, how users inspect/edit/delete that memory, and where personalization stops before it starts influencing business decisions in ways users can’t…

@AGASTYA SHARMA Rebekka’s right—and this has moved further in that direction. Rovo parent agents can now delegate to multiple specialized subagents, including in parallel, then consolidate their results. What I haven’t seen documented yet is a built-in “debate/consensus” mechanism where agents formally critique and vote on…

@AGASTYA SHARMA timely question—Rovo now has persistent Memory Management separate from the conversation context window. It includes personal implicit memory from Teamwork Graph activity and explicit facts/instructions saved from chats. Agent Instructions and Knowledge still handle shared organizational behavior/RAG. So…

@Phil Eichmiller welcome to the community. I think the distinction is between Atlassian’s internal service monitoring and customer-visible agent observability. Rovo already has service health monitoring/status, but Agent Insights currently shows usage—not per-action success/failure rates or anomaly alerts. Your request…

@Justin Messner since the flow is still running but missing from the Automation library, I’d check Studio → Audit log and search for the flow name. Atlassian documents the Audit log as the place to locate flow executions and inspect their details. Studio-created flows should normally live in the Automation library, so if…

@Mahanth Prudhvi P the demos are directionally accurate, but I’d describe Rovo Dev today as highly agentic, not fully autonomous. It can take Jira context, generate code and create a PR, while Rovo Dev reviews PRs in Bitbucket/GitHub. Atlassian still documents human review before commit/merge. I also don’t see supported…

@rachit_sharma thanks, that architecture helps. I can’t find Atlassian documentation that publishes a separate Studio Automation egress range or confirms a narrower Studio-only CIDR set. I’d therefore avoid assuming Jira Automation ranges are identical without Support confirmation. Your incoming webhook is separate—it’s…

@Julian Becher One update: individual agents can now be removed from Jira work items via Studio → Agents → [agent] → Surfaces → Work items → Off. However, I still don’t see a supported setting to hide the entire Agents section for one project while keeping Rovo enabled. ROVO-702 is tracking broader agent-visibility…