What leaders and teams rolling out Confluence report, with every finding tied to its evidence.
Read the findingsPractitioner sentiment, leaders and teams
+8 Mixed from 36 sources that take a side
How this figure is madeFrom 36 authors in 30 discussions. Run a pilot with one team to measure how much of its planning and writing stays in the tool after a month.
Jan 2025 to Oct 2026.
101 sources from practitioners, by month and sentiment.
Team and company accounts lean slightly positive. All 8 that discuss Jira links praise them, and all 6 that discuss data raise it, from the data contribution default to a published Rovo exfiltration test. Search draws complaints from 3 of the 5 that discuss it. On whether to use Rovo or their own AI tools, they lean 6 to 3 toward their own.
Positive, mixed and negative sources
The score counts each source once, as the split does. See How the numbers work.
See the evidenceBelow: 3 praise themes, 2 concerns and 1 disagreement.
Counted for Leaders and teams rolling it out, from 37 sources. Change group
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
Counted for Leaders and teams rolling it out.
Positive
Clara C., G2 reviewer
G2 review: Confluence + Jira Links Keep Decisions Clear and Easy to TraceG2 review, republished on AWS Marketplace
Linking Confluence pages to Jira tickets ended the team's repeated questions about why decisions were made and made onboarding easier, but search sometimes surfaces an old version of a page.
Positive
Ankush, Shorthills AI team lead
Project Management with Confluence and JiraTeam case study, YouTube
Ankush describes how his distributed technology team uses Confluence and Jira to coordinate work across four countries and time zones.
"Project Management | Confluence | Jira | Case Study…"
Positive
Talha Hussain, PeerSpot reviewer
Manage projects effectively with seamless task tracking and integration, but deployment requires familiarityIndependent review, PeerSpot
After five years, the reviewer's team runs all project management on Atlassian tools and uses Confluence mainly for its Jira integration. Cost is a factor because new projects and staff need extra purchases.
Positive
Venkata Raghuram Challa, PeerSpot reviewer
Real-time editing and seamless integration enhance documentation managementIndependent review, PeerSpot
Real-time editing, comments, and Jira tickets pulled straight into pages make Confluence useful for the reviewer's teams. They want AI built in and more editing options, and find the cost reasonable for one platform.
Positive
Robert Hean, Hean Tech consultant
One tool your support team needsPractitioner guide, YouTube
Robert Hean explains how support teams use structured Confluence spaces, reusable content, and Jira integration to align responses and document solutions.
"One tool your support team needs | Confluence for Support Teams…"
Positive
Shivam Kadwade, Scrum team member
SCRUM Automation with Jira, Rovo, Loom, and ConfluencePersonal blog post, Medium
The author's Scrum team uses Rovo with Jira and Loom to draft status documents, analyze retrospectives in Confluence, turn tasks into tickets, and run a triage agent for Jira hygiene.
Positive
BlondBot, Reddit user, documentation department
Rovo success storiesReddit post
The documentation team produced a release's notes in five minutes by copying the last page and telling Rovo to write from a list of Jira tickets and the product docs.
Positive
Patrik Rosendahl, PeerSpot reviewer
Collaborative workspace has improved cross-team documentation and now supports structured projectsIndependent review, PeerSpot
Links between Jira and Confluence and per-company areas with access control are what the reviewer values. Duplicate pages across departments make search return fifteen pages on one project, which they trace to missing structure.
Counted for Leaders and teams rolling it out.
Positive
Robert Hean, Hean Tech consultant
One tool your support team needsPractitioner guide, YouTube
Robert Hean explains how support teams use structured Confluence spaces, reusable content, and Jira integration to align responses and document solutions.
"One tool your support team needs | Confluence for Support Teams…"
Positive
muzani, Hacker News commenter, self-described
Comment on: Ask HN: Is every company's internal wiki just broken by default?Hacker News comment
The commenter's team considers Confluence the best tool it has, with some of the best search; people prefer writing in Google Docs, whose search is much worse.
Positive
Rabindra K Maharana, PeerSpot reviewer
Editing features improve document accessibilityIndependent review, PeerSpot
Confluence serves the reviewer's project as one repository for technical documentation and team structure across India and Germany, with quick copy-and-edit; they rate it eight out of ten.
Positive
Patrik Rosendahl, PeerSpot reviewer
Collaborative workspace has improved cross-team documentation and now supports structured projectsIndependent review, PeerSpot
Links between Jira and Confluence and per-company areas with access control are what the reviewer values. Duplicate pages across departments make search return fifteen pages on one project, which they trace to missing structure.
Positive
Ankush, Shorthills AI team lead
Project Management with Confluence and JiraTeam case study, YouTube
Ankush describes how his distributed technology team uses Confluence and Jira to coordinate work across four countries and time zones.
"Project Management | Confluence | Jira | Case Study…"
Positive
Venkata Raghuram Challa, PeerSpot reviewer
Real-time editing and seamless integration enhance documentation managementIndependent review, PeerSpot
Real-time editing, comments, and Jira tickets pulled straight into pages make Confluence useful for the reviewer's teams. They want AI built in and more editing options, and find the cost reasonable for one platform.
Counted for Leaders and teams rolling it out.
Positive, 4
Positive
Shivam Kadwade, Scrum team member
SCRUM Automation with Jira, Rovo, Loom, and ConfluencePersonal blog post, Medium
The author's Scrum team uses Rovo with Jira and Loom to draft status documents, analyze retrospectives in Confluence, turn tasks into tickets, and run a triage agent for Jira hygiene.
Positive
Own_Mix_3755, Reddit commenter
Comment on: Struggle to find value in Rovo what do you think?Reddit comment
The commenter's company uses Rovo mostly as background agents that triage tickets, reply when the knowledge base has a match, and propose similar tickets, with no extra subscription on Premium.
Positive
anyelo-cp, Reddit commenter, Jira admin and automation consultant
Comment on: Anyone actually using Rovo daily?Reddit comment
As admin, the commenter runs Rovo agents on triggers across several projects and estimates they save the company thousands of hours a year.
Positive
atonse, Founder and CEO of Kaizen
Comment on: What the heck is MCP? And why is everybody talking about it?Hacker News comment
Within a week of trying it, the commenter used the Atlassian MCP server to organize a backlog, merge tickets into epics, comment on tickets from commit summaries, and transition and reassign them.
Mixed or negative, 2
Negative
Dariusz Szwarc, GitHub user at TomTom
updateConfluencePage / createConfluencePage unusable for large pagesGitHub issue on atlassian/atlassian-mcp-server
The MCP page tools take the whole page body inline. A 40 to 70 KB design doc forces the agent to regenerate about 15,000 tokens of page JSON for a one-sentence change. That makes agent editing of real documents impractical.
Negative
verdverm, Hacker News commenter, self-described
Comment on: Jira launches system for AI-native software developmentHacker News comment
The commenter's team wants to choose its own models and avoid Rovo. It found Atlassian's twg CLI help text wrong and its skills about 70,000 tokens, and now calls Atlassian's API directly.
Every concern practitioners raise, most raised first.
Counted for Leaders and teams rolling it out.
Negative
Hefty-Possibility625, Reddit user, Atlassian organization admin
Rovo Studio Update - Please help me get out of a documentation loop, how do I disable this new role?Reddit post
Atlassian granted the Rovo Studio user role to every existing user, and the admin cannot find where to remove it, which matters because of an unfixed data exfiltration report.
Negative
ExoticPearTree, Hacker News commenter answering security questions at work
Comment on: Atlassian Rovo Exfiltrates Data, Bypassing ControlsHacker News comment
The commenter fielded a security question about why an AWS IP address was downloading all of the company's documents after Rovo was connected to Google Docs or SharePoint.
Negative
PromptArmor, AI security research firm
Atlassian Rovo Exfiltrates Data, Bypassing ControlsSecurity research blog post, PromptArmor
A hidden prompt in an uploaded file made Rovo send Jira tickets and Confluence documents to an outside URL with no human approval, even with web search turned off. Atlassian acknowledged the May 2026 report and had sent nothing further by August.
Negative
kevcampb, Hacker News commenter administering Atlassian instances
Comment on: Atlassian enables default data collection to train AIHacker News comment
The commenter reports that free and paid customers are opted in to having Confluence pages and Jira tickets used for AI training by default. The opt-out setting did not appear on any of their instances.
Negative
carld, Hacker News commenter with Atlassian Administration access
Comment on: Atlassian enables default data collection to train AIHacker News comment
Looking in Atlassian Administration under Security, the commenter could not find the Data contribution setting and asks whether the opt-in has no opt-out.
Negative
rdedev, Hacker News commenter
Comment on: Atlassian enables default data collection to train AIHacker News comment
Replying to a question about sensitive tickets and training, the commenter notes that manufacturing investigation reports at the pharma company they work for sit in Jira tickets and Confluence pages.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.From August 17, 2026, Free and Standard default to contributing in-app data unless an admin turns it off. Premium and Enterprise default to off. Metadata contribution is always on except on Enterprise, where admins can disable it. Data contribution settings
Open them in the recordCounted for Leaders and teams rolling it out.
Raised as a concern, 3
Negative
deanc, Hacker News commenter advising client organisations
Comment on: Claude IntegrationsHacker News comment
Working with many organizations, the commenter no longer recommends Confluence to clients because keyword search makes large instances useless, and wants an LLM to ask questions of the wiki.
Positive
Clara C., G2 reviewer
G2 review: Confluence + Jira Links Keep Decisions Clear and Easy to TraceG2 review, republished on AWS Marketplace
Linking Confluence pages to Jira tickets ended the team's repeated questions about why decisions were made and made onboarding easier, but search sometimes surfaces an old version of a page.
Positive
Patrik Rosendahl, PeerSpot reviewer
Collaborative workspace has improved cross-team documentation and now supports structured projectsIndependent review, PeerSpot
Links between Jira and Confluence and per-company areas with access control are what the reviewer values. Duplicate pages across departments make search return fifteen pages on one project, which they trace to missing structure.
Discussed without concern, 2
Positive
sssst_stump, Reddit commenter
Comment on: Struggle to find value in Rovo what do you think?Reddit comment
Staff at the commenter's company will not search in Confluence, so Rovo in Slack lets them find docs; its main value is searching GitHub, Drive, and Slack from Confluence.
Positive
muzani, Hacker News commenter, self-described
Comment on: Ask HN: Is every company's internal wiki just broken by default?Hacker News comment
The commenter's team considers Confluence the best tool it has, with some of the best search; people prefer writing in Google Docs, whose search is much worse.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Rovo Search in Atlassian apps combines Confluence and Jira results with connected apps, follows each user's permissions, and uses no Rovo credits. How Rovo credits work
Open them in the recordStatements this group's sources agree on, then the ones close to agreement.
For leaders and teams rolling it out, no statement reaches 5 sources from 3 authors.
Questions the sources split on, with the count on each side.
Evidence remains mixed
Rovo, 3 sources
Rovo provides answers and writing help inside Confluence and Jira, with agents acting on the same content.
Own AI tools, 6 sources
Claude, Cowork, or the author's own agents connect through the MCP server, CLI, or API.
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on Leaders and teams rolling it out.
37 sources. These accounts focus on team and company accounts: how Confluence sits next to Jira, how Rovo agents work on a team's tickets and pages, and how Atlassian uses company data.
64 sources. These accounts focus on one person's daily use: finding things, writing in the editor, and the Rovo features that now sit on every page.
101 sources. This gives the broadest read, but combines one person's wiki habits with team rollouts that can reach different conclusions.
101 sources from practitioners, by the context they work in. Filled rows count for this group.
Emphasizes Search, page speed, AI buttons, and Rovo answers
Emphasizes Rovo answers across apps, and own AI through the API
Emphasizes Jira links, Rovo agents on tickets, admin controls, and regulated data
Emphasizes Data contribution settings, connectors, and the move off Data Center
Emphasizes Company-wide AI rollout and the cloud-only move
What changes with scale. Individual users talk most about finding pages, slow loads, and AI they did not ask for. Team and company accounts shift to Confluence's structure and Jira links, and to what Atlassian does with company data and where it is hosted.
Where this group's sources were published.
Counted for Leaders and teams rolling it out, from 37 sources. Change group
51 sources for this group, 14 of them documentation
Older evidence is retained when it still applies. Sources about Atlassian Intelligence before Rovo, or about settings Atlassian has since shipped, stay in the history, marked Needs a recheck.
See sources by originWho each source is, how it knows, whether it still applies and what it counts toward.
Newest first, on its own page. Every count above opens its sources there.
Read all 115 sourcesAbout this read
A running review of what people using Confluence at work report, from individual users to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Flagged for a recheck, of the sources that take a side: leaders and teams 5 of 36, individual users 0 of 64, all users 5 of 100.
Each row opens its sources for the group you are reading.
| Finding | Leaders and teams rolling it out | Individual users | All users | Sources |
|---|---|---|---|---|
| Current readCurrent sentiment | 18 positive, 3 mixed, 15 negative | 20 positive, 9 mixed, 35 negative | 38 positive, 12 mixed, 50 negative | Sources |
| PraiseAnswers Across Confluence & Jira | 4 of 4 positive (under the minimum) | 12 of 14 positive | 16 of 18 positive | Sources |
| PraiseWorks With Jira | 8 of 8 positive | 2 of 2 positive (under the minimum) | 10 of 10 positive | Sources |
| PraisePages, Spaces & Permissions | 6 of 6 positive | 5 of 9 positive | 11 of 15 positive | Sources |
| PraiseAgents, Automation & MCP | 4 of 6 positive | 4 of 5 positive | 8 of 11 positive | Sources |
| PraiseWriting & Summaries | 3 of 4 positive (under the minimum) | 5 of 9 positive | 8 of 13 positive | Sources |
| ConcernConfluence Search | 3 of 5 raise it | 11 of 12 raise it | 14 of 17 raise it | Sources |
| ConcernSpeed & Page Loads | 1 of 1 raise it (under the minimum) | 11 of 12 raise it | 12 of 13 raise it | Sources |
| ConcernAI Placement & Opt-Out | 2 of 2 raise it (under the minimum) | 11 of 11 raise it | 13 of 13 raise it | Sources |
| ConcernAnswer Accuracy | 3 of 3 raise it (under the minimum) | 9 of 9 raise it | 12 of 12 raise it | Sources |
| ConcernData Use & Security | 6 of 6 raise it | 1 of 3 raise it (under the minimum) | 7 of 9 raise it | Sources |
| ConcernCloud-Only Move | 2 of 3 raise it (under the minimum) | 1 of 2 raise it (under the minimum) | 3 of 5 raise it | Sources |
| ConsensusClean pages decide answers | 2 supporting (under the minimum) | 6 supporting (below threshold) | 8 supporting (below threshold) | Sources |
| ConsensusOther AI tools reach Confluence | 4 supporting (under the minimum) | 5 supporting (below threshold) | 9 supporting (below threshold) | Sources |
| DisagreementShould your team use Rovo, or point its own AI tools at Confluence? | Rovo 3, Own AI tools 6 | Rovo 6, Own AI tools 7 | Rovo 9, Own AI tools 13 | Sources |
| DisagreementDoes Rovo save time or cost it? | Saves time 3, Costs time 1 (under the minimum) | Saves time 5, Costs time 6 | Saves time 8, Costs time 7 | Sources |
| Current readEvidence mix | 51 sources | 78 sources | 115 sources | Sources |
GILD's checks of claims against official documentation, kept apart from the source counts.
