Confluence Reviews & Product Details

As a QA engineer, Confluence is where my entire testing workflow lives. What I like best is the Jira integration my test case documents, bug analysis reports, and requirement gap analyses all link directly to the tickets they relate to, and I can embed live Jira issue tables in a page so a feature's test coverage status is always current without manual updates. Page templates are the other big win: I've standardized formats for test plans and PRD review docs, so every feature gets documented the same way and stakeholders know exactly where to find what they need. It also made my own onboarding faster when I joined the existing QA space gave me feature context in days that would otherwise have taken weeks of asking around. Inline comments have quietly become essential too: when I document a requirement gap or an edge case question, product managers respond right on that line, and the decision stays attached to the doc for future reference. Version history has saved me more than once when tracing when and why a requirement changed between releases.And on the rare occasions I've been stuck, Atlassian's documentation and community forums have had an answer every time I've never needed to raise a support ticket for day-to-day usage. Review collected by and hosted on G2.com.

Search is my daily frustration. When I need to find a specific test plan or an older bug analysis doc, Confluence search often surfaces outdated drafts or duplicate pages first, so I've resorted to bookmarking key pages instead of trusting search which defeats the purpose of a knowledge base. The editor's table handling is my second complaint: my test case documents are table-heavy, and restructuring columns, copy-pasting rows from spreadsheets, or working with large tables is slow and error-prone compared to Excel or Sheets. Long documentation pages also become sluggish to edit, which I hit regularly with detailed test coverage docs. Finally, useful capabilities like AI-powered search and content summaries sit behind the Premium tier, so teams on Standard don't get help with exactly the problem (findability) the product most needs to solve. Better search relevance and native stale-page detection would fix most of this Review collected by and hosted on G2.com.

I like how Confluence is used for everyday team collaboration, including meeting notes and brainstorming sessions. The dynamic collaboration is great, allowing you to work with as many colleagues as you want. I appreciate the traceability with a good audit and version control. The clean, minimalistic design with no noise makes it ready to go without much configurational effort. The ease of use is a big plus, and the team can start using it right away. I also enjoy the seamless integration with Jira, which makes it much better to use together. Review collected by and hosted on G2.com.

Sometimes, the content can get too messy and outdated. We'd love to have more possibilities to alert us on outdated or unconsulted content to keep our documents and spaces healthier and less cluttered. Review collected by and hosted on G2.com.

I’ve used Confluence a lot for project documentation, test-related docs, release notes, meeting notes, and sharing technical information with the team. What I like most is that everything stays in one place, so I don’t have to dig through emails or multiple folders just to find an older document.

It also integrates really well with Jira. When I’m looking at a user story or a bug, I can usually jump straight to the related documentation without wasting time. That’s been especially helpful during sprint planning, testing, and production releases.

Another plus is that multiple people can update the same page without ending up with separate versions of the same document. It helps keep information current, and everyone is working from the same source instead of maintaining different copies. Review collected by and hosted on G2.com.

I don’t have any major issues with it, but when a project has been running for a long time, the amount of documentation can grow pretty large. At that point, finding older pages sometimes takes a bit of digging unless everything is well organized.

Formatting tables or longer documents can also be a little frustrating at times, especially when I’m trying to get everything to line up neatly. It’s not something I run into every day, but I’ve noticed it on a few occasions.

Other than that, it’s been a reliable documentation tool overall. Review collected by and hosted on G2.com.

It helps us have one north star, a single repository where we can keep all our documentation, results, and other materials in one place. It ensures we’re all working from the same source, and it’s very easy to set up. You can also tie it in to automate work in Jira. Overall, it’s easy to use, and even if there’s churn, we still have the documentation. Review collected by and hosted on G2.com.

I have to say there’s a learning curve when you’re first figuring out how to use it. At times the UX feels too reactive: trying to move a paragraph can create multiple rows, and other times you try to move something and it gets wiped off the page. I also didn’t even know how to edit at first, so for new users the learning curve is definitely there. Review collected by and hosted on G2.com.

What I like most about Confluence is that it centralizes all of our project documentation and technical specs in one place, so everything is easy to find and reference. It also integrates seamlessly with Jira, which makes it straightforward to link requirements directly to tickets and follow development progress. On top of that, the real-time collaborative editing is a big plus—it’s much easier for the team to brainstorm together and keep documentation current without running into version-control headaches. Review collected by and hosted on G2.com.

The search functionality can be incredibly frustrating. Even when you search for the exact title of a page, the algorithm often ranks older, archived documents or unrelated team spaces higher than what you actually need, forcing you to rely heavily on direct links.

Additionally, the page editor can feel a bit sluggish and clunky when working with massive, media-heavy documents or complex nested tables. The markdown support is also a bit finicky; it doesn't always translate perfectly from standard IDE markdown shortcuts, which adds minor friction when developers try to quickly copy and paste documentation from their code repositories. Review collected by and hosted on G2.com.

The best part about confluence is it provides the centralized and organized workspace for documentation, collaboration and knowledge sharing.

I particularly like easy to editor tool, easy to integrate with Jira and other Atlassian tools with real time collaboration

The performance of this tool is good, technical support and onboarding process is pretty much easier Review collected by and hosted on G2.com.

Confluence is overall awesome tool but performance can feel down occasionally with large pages and managing content structure across multiple spaces become more complex to manage and need to improve the search accuracy and navigation could enhance the tool performance to the next level Review collected by and hosted on G2.com.

What I like most about Atlassian Confluence is how it keeps team knowledge centralized and easy to find. It serves as a structured hub where meeting notes, project documentation, and company guidelines can all live in one place, which makes information much more accessible. The integration with Jira, along with real-time collaborative editing, also helps the team stay aligned and cuts down on constant back-and-forth communication. Review collected by and hosted on G2.com.

The biggest drawback I’ve noticed with Atlassian Confluence is how quickly it can become cluttered once a large number of pages start piling up. If teams aren’t disciplined about structure and organization, it’s easy for things to get messy and for important information to become hard to find. On top of that, working with longer documents doesn’t always feel as smooth as I’d expect, and the page editor can sometimes seem slow or a bit unintuitive—especially when I’m dealing with more complex formatting. Review collected by and hosted on G2.com.

As a Data Operations Specialist, I use Confluence daily as our team's central knowledge repository. Over the past year, I've used it to create and maintain SOPs, document Salesforce account creation processes, data enrichment workflows, duplicate management procedures, and governance guidelines for teams across Strategy Ops, Field Ops, and Marketing Ops.

One feature I use frequently is templates and expandable sections to keep large process documentation organized. We also use Confluence to track project updates, document integration architecture, and maintain process ownership across systems like Salesforce, ZoomInfo, D&B, and Marketo.

What I value most is that it creates a single source of truth and reduces back-and-forth communication. Instead of asking teams for process details repeatedly, people can access updated documentation directly. Review collected by and hosted on G2.com.

Searching for older content can sometimes be difficult when pages are not consistently tagged or organized. As documentation grows across teams, content structure becomes very important. Review collected by and hosted on G2.com.

I thought it was very user-friendly and found project tracking easy. For example, this space allows the engineers and I to track the statuses of Jira tickets. We also are able to add resources and SOPs in folders to share with the wider organization. Review collected by and hosted on G2.com.

I think the search feature could be better. As of right now, the search feature doesn't exactly provide what I am looking for. This is especially true when trying to locate bugs that may sound the same but are not. I also think the website could be a little more intuitive. It only really starts to make sense once you have worked in it for awhile. Review collected by and hosted on G2.com.

What I like most about Confluence is how effectively it serves as a living, single source of truth. Its native, bi-directional integration with Jira keeps our project tracking and technical documentation aligned, so they don’t drift out of sync. With modern Atlassian Intelligence features that provide instant summaries, plus a robust macro engine, we can maintain strict technical governance while still making the documentation easy to navigate and accessible for non-technical stakeholders. Review collected by and hosted on G2.com.

The permissions management architecture comes with a steep learning curve. Setting up granular access control—especially when I’m trying to securely isolate spaces for external stakeholders or guest vendors—feels tedious and often requires ongoing auditing to make sure nothing is accidentally exposed or leaked. Review collected by and hosted on G2.com.