Skip to main content

Research

What People Report After Rovo Arrived in Confluence

Across 101 public accounts, Rovo's answers earn the most praise and keyword search the most complaints. The accounts also cover AI placed on every page, wrong answers, and data use.

Reading time
3 min read
Sources
16 cited
In this piece
Confluence+8 Mixed

Key findings

  1. 16 of the 18 accounts that discuss Rovo's answers across Confluence, Jira, and connected apps are positive.
  2. All 13 accounts that discuss AI buttons, prompts, and summaries on every page raise them as a problem. All 12 that discuss accuracy report wrong or invented answers.
  3. 14 of the 17 accounts that discuss Confluence's own search raise it as a problem, and 12 of 13 that discuss page speed report slow pages.
  4. Of the 21 accounts that take a side on Rovo versus their own AI tools, 12 prefer their own and 9 prefer Rovo. Those that take a side on whether Rovo saves time split 8 yes and 7 no.
  5. Team and company accounts, 36 of the 101, split across 18 positive, 3 mixed, and 15 negative. All 6 that discuss Jira links praise them, and all 6 that discuss data raise it as a concern.

People who use Rovo's answers like them. Confluence's own search draws the most complaints, followed by how Atlassian placed AI across Confluence, then wrong answers and slow pages. Accounts that compare Rovo with their own AI tools lean toward their own.

Answers beat search

Users who rely on Rovo make it their first stop. One new employee asks it about 20 times a day and gets links to internal docs. A head of account management drafts client answers from tickets, Confluence, and the client wiki before handing them to support. Several users rate Rovo above the keyword search beside it.

Confluence's keyword search draws the sharpest criticism. Users report missing pages, PDFs ranked above pages, and results that ignore a document they just viewed.

Teams use agents on tickets and pages

Team accounts describe Rovo taking over repeat work. A documentation department wrote a release's notes in five minutes from a list of Jira tickets. One company runs Rovo agents in the background to triage incoming tickets and reply when the knowledge base has a match, with no extra subscription on Premium. An admin estimates that agents on triggers across several projects save the company thousands of hours a year.

Where Rovo goes wrong

Critical accounts cite invented meetings, an edit that erased a page, a Jira function that does not exist, and wrong Atlassian instructions. One user finds about 80% of ticket summaries correct, and the rest omit details the tickets never contained.

AI on every page

Individual users object to Rovo buttons, the "Press space to Ask Rovo" prompt, and summaries placed across Confluence and Jira. Hiding them with uBlock now makes the editor lag or crash. Organization admins can block Rovo per app, and individual users have no opt-out. One admin found the Rovo Studio role granted to every existing user.

Rovo or your own AI

Accounts that choose another tool name Claude Code or Claude Desktop connected to Confluence, Cowork with MCP, GitHub Copilot, or a team's own MCP server. Rovo supporters cite its place inside Jira and Confluence and the credits included in the plan. Outside tools that request enriched Teamwork Graph context draw on the same Rovo credit pool.

Methodology

GILD read 101 public accounts, published from January 26, 2025 to October 20, 2026, and recorded the themes each one discusses. These comprise 59 Hacker News comments, 24 Reddit posts and comments, 1 Atlassian Community comment, 4 PeerSpot reviews, 1 G2 review, and 3 Medium posts. The rest are 1 security research post, 2 GitHub issues, and 2 X posts. Many of the Hacker News accounts come from threads about Atlassian's AI push and data policy, which tilts the set toward critics. PromptArmor's published Rovo exfiltration test is the record's one security test. Every figure here comes from those accounts or from the Atlassian pages linked in Sources.

Products in this piece

Sources

Official documentation
5
Public source
11
  1. Atlassian Support: Rovo SearchOfficial documentationsupport.atlassian.com
  2. Atlassian Trust Center: Rovo AI security and trustOfficial documentationatlassian.com
  3. Atlassian Support: Manage Rovo accessOfficial documentationsupport.atlassian.com
  4. Atlassian Support: Get started with the Atlassian MCP serverOfficial documentationsupport.atlassian.com
  5. Atlassian Support: Data contribution settingsOfficial documentationsupport.atlassian.com
  6. Hacker News comment on sending consultants to Rovo first (Jun 5, 2026)Public sourcenews.ycombinator.com
  7. Hacker News comment on Rovo finding 3 of 60 Confluence articles (Mar 12, 2026)Public sourcenews.ycombinator.com
  8. Hacker News comment on Rovo summaries inventing meetings (Feb 3, 2026)Public sourcenews.ycombinator.com
  9. Hacker News comment on Rovo erasing a Confluence page (Mar 12, 2026)Public sourcenews.ycombinator.com
  10. Reddit r/atlassian: a documentation team writes release notes with Rovo in five minutes (Jun 4, 2026)Public sourcereddit.com
  11. Reddit r/atlassian comment on Rovo agents that triage incoming tickets (Aug 27, 2026)Public sourcereddit.com
  12. Reddit r/atlassian: how accurate Rovo is when tickets are incomplete (Sep 2, 2026)Public sourcereddit.com
  13. Reddit r/atlassian: hiding Rovo with uBlock breaks the Confluence editor (Sep 28, 2026)Public sourcereddit.com
  14. Reddit r/atlassian: an admin finds the Rovo Studio role granted to every user (Sep 30, 2026)Public sourcereddit.com
  15. Reddit r/atlassian: comparing Rovo with Claude Code over MCP (Aug 27, 2026)Public sourcereddit.com
  16. Hacker News comment on the data contribution setting missing from admin (Apr 20, 2026)Public sourcenews.ycombinator.com