Confluence

What do you like best about the product?

I use Confluence as a centralized knowledge base for documentation, project information, and team collaboration. It helps maintain requirements, test plans, release notes, and technical documentation all in one place, making information easy to find and share across teams. For QA engineering teams, Confluence allows us to maintain documentation that evolves with product versions, including test cases, automation frameworks, onboarding guides, and known issues. The integration with Jira is particularly useful as it connects documentation directly with development and testing activities, creating a single place for information. I value the page hierarchy and structured documentation capability the most. It organizes content into spaces, with parent and child pages, which makes navigation easy and prevents information from being lost or scattered. I frequently use the integration with Jira to link Jira tickets, epics, and reports directly into documentation, keeping context in one place. I also utilize their templates for standardizing meeting rules, release documentation, test plans, and project requirements. This combination of structured documentation and Jira integration makes Confluence extremely valuable. Additionally, Confluence helps us track changes and restore previous versions if needed, which is great if something is edited by mistake.

What do you dislike about the product?

The search functionality in Confluence is generally not good at finding very specific information, which sometimes requires more time and multiple searches. Additionally, large spaces with a lot of pages, like when we have a very big documentation or whole project documentation, take a long time to load.

What problems is the product solving and how is that benefiting you?

Confluence is my go-to for centralizing knowledge and ensuring consistent documentation across teams. It reduces time spent searching for information, integrates seamlessly with Jira, and helps maintain evolving documentation, making onboarding easier and cutting dependency on scattered documents.

What do you like best about the product?

Confluence’s best feature for me is its capability to centralize all documentation and collaboration among various teams on one platform. This makes it easy for our team to keep track of projects, meeting minutes, technical documentation, and even process information in an organized manner. The combination of Confluence with Jira is very useful, as it links project management with document management and increases visibility. Other features that I find appealing include commenting, mentions, templates, version control, and page permissions.

What do you dislike about the product?

A feature of Confluence that I am not very fond of is the difficulty in navigating through an environment with numerous spaces and pages that lack any sort of organization or governance. The search engine may yield results that are hard to understand at times, particularly for organizations with vast documentation. Moreover, when pages consist of lots of macros or huge amounts of content, editing can be slow. There are some advanced features that require the use of add-ons, making things more complicated and expensive.

What problems is the product solving and how is that benefiting you?

The major use that we made of Confluence was to compile all our project documents into one place. We had previously faced problems with having information scattered in various forms of files, emails, and folders, making it hard to locate or update any information at hand. However, after the use of Confluence, it was more convenient for team members to work together, exchange information, record their meeting notes and other processes, etc.

What do you like best about the product?

It allows building an internal database of articles, instructions, knowledgebase, etc.

What do you dislike about the product?

Navigating between spaces is unintuitive. Search could also be more intelligent.

What problems is the product solving and how is that benefiting you?

Sharing internal information across the company, with possibilities of setting granular access rights.

What do you like best about the product?

Confluence has been best tool for documentation purpose , smart accessibility features. Structuring format.

What do you dislike about the product?

It has almost zero downtime . And always a lower env instance available to view required documents hosted

What problems is the product solving and how is that benefiting you?

How it can control the accessibility, sharing of documents among peers. Look and feel of application

What do you like best about the product?

I like that Confluence is so integrated with many things I use. The variety of plugins and add-ons on Confluence unlocks so many creative options for our teams. I also appreciate that it's so fluid, allowing teams to be liberal about their spaces without being confined like other content management systems. The plugins and integrations help me integrate data and visualizations and make Confluence really valuable for collaboration, which is key when working with many. The initial setup of Confluence was very easy, super simple, and friendly.

What do you dislike about the product?

I believe Atlassian could work more on integrating AI and automation in Confluence. Also, handling larger pages on Confluence could be streamlined much better.

What problems is the product solving and how is that benefiting you?

I use Confluence for sharing documentation and guides. It solves issues with organization, administration, and helps with clear team boundaries, security, and audits. The plugins and integrations, inside and outside the Atlassian ecosystem, make collaboration smoother and Confluence more valuable.

What do you like best about the product?

I love Confluence as a product, but its architecture and how it works are the best things. The way we can search across the organization at times and at others search within a specific space makes it a go-to place to debug anything at our firm. It stores over a decade of technical documentation, making it a big asset to agentic coding since we can use Confluence MCP server to provide more detailed and firm-specific context to our models. I also like that no setup was required and it worked out of the box for me. the UI is awesome & how the integrates with the whole SDLC ecosystem is the main thing that makes it worth it

What do you dislike about the product?

I feel like the search is mostly lexical right now. If there were some semantic-search upgrades, that would be really awesome—especially if it also included an inbuilt chatbot. I also think they should offer a native MCP server rather than relying on firms to create their own, and that the search experience should move toward semantic, vector-based searching.

At times it becomes really hard to navigate through a clutter of documents. If there were a solution that could streamline that experience and make it easier to find what I need, it would be awesome.

What problems is the product solving and how is that benefiting you?

I use Confluence to centralize documentation for our team. It acts as a comprehensive wiki, storing technical decisions and history, which helps in documenting both software-related and unrelated information, like weekly support schedules. it improves communication & hence team's performance in general, for some issues you dont need to reach out to senior members you can use confluence & deal with it yourslef

What do you like best about the product?

What I like best about Confluence is how easy it makes collaboration and documentation across teams. Everything stays in one place, whether it is meeting notes, project updates, SOPs, or technical documentation, so it becomes much easier to find information without digging through emails or chats.

I also like how flexible and organized it is. Creating pages, using templates, linking related content, and integrating with Jira helps teams stay aligned and work more efficiently.

The real time collaboration and version history are also really useful because updates and reviews become much smoother while still keeping track of changes.

What do you dislike about the product?

One thing I dislike about Confluence is that it can become cluttered over time if teams do not maintain a proper structure. Finding the right page or latest document sometimes takes extra effort, especially in large workspaces with a lot of outdated content.

The editor is good for general documentation, but formatting and page organization can occasionally feel limiting compared to more modern tools. Performance can also slow down when pages become too large or contain multiple integrations and macros.

Another challenge is that onboarding new users takes some time because there are many features, permissions, and navigation layers to understand.

What problems is the product solving and how is that benefiting you?

Confluence helps solve the problem of scattered information across teams. Earlier, important details were spread across emails, chats, spreadsheets, and shared drives, which made it difficult to track updates or find the latest information. Confluence brings everything into a single centralized place, making collaboration and knowledge sharing much easier.

It has also helped improve transparency and alignment within projects. Teams can document requirements, meeting notes, decisions, and progress updates in one place, so everyone stays on the same page without constant follow ups.

For me, the biggest benefit is saving time and improving team efficiency. It reduces duplication of work, makes onboarding easier, and gives quick access to historical context whenever needed.

What do you like best about the product?

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.

What do you dislike about the product?

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.

What problems is the product solving and how is that benefiting you?

Overall, Atlassian Confluence helps prevent team knowledge from getting lost or scattered. Rather than having important details buried in chat threads or saved on individual devices, everything—from meeting notes to team processes—can live in one centralized place. That makes it easier to avoid duplicated effort and reduce the risk of relying on outdated information. It also saves time, since there’s less need to keep asking teammates where documents are stored.

What do you like best about the product?

I mainly use Confluence for technical documentation and for sharing internal knowledge across my team. One of the most valuable features for us is the version history, since it lets us track changes over time and roll back updates when needed—especially during large project migrations or when requirements change.

Collaborative editing has also noticeably improved our workflow. It’s particularly helpful when multiple developers and stakeholders need to work on the same documentation at the same time, without creating duplicate pages or causing confusion.

I’ve also found the templates very useful for keeping project documentation organized, including API references, migration plans, and operational runbooks. They cut down the time we’d otherwise spend starting documents from scratch and help keep information consistent and standardized across teams.

Another big advantage is how easy it is to maintain a centralized knowledge base for onboarding new team members, which has reduced our reliance on repeated knowledge-transfer sessions.

What do you dislike about the product?

One area where Confluence could improve is its template library. The existing templates are solid for general documentation, but for growing engineering teams working with complex systems, there’s room for more practical, modern use cases.

For instance, during legacy application migrations, documentation can become overwhelming very quickly. Architecture docs, dependency maps, migration plans, risk assessments, deployment steps, and operational notes start piling up, and it becomes hard to keep a consistent structure across teams. Purpose-built templates for scenarios like legacy modernization, microservice migration, cloud migration, or production rollout planning would make this kind of documentation far easier to organize and maintain.

Navigation and knowledge discovery also become challenging as documentation scales. Once a project grows to hundreds of pages (200–500+), new team members often struggle to understand the overall system without spending a lot of time digging through scattered pages.

An AI-powered overview or knowledge summary feature could add a lot of value here. For example, Confluence could generate a high-level overview page or a visual knowledge map that summarizes the purpose of a space or section, the major systems involved, key workflows, dependencies, and the most important related documents. This would improve onboarding, reduce time spent searching, and help teams grasp the bigger picture without manually navigating through hundreds of pages.

What problems is the product solving and how is that benefiting you?

Confluence has been very helpful for documenting deployment processes and keeping technical documentation structured and centralized. Our team uses it regularly to capture release steps, environment configurations, troubleshooting guides, and operational procedures, and it has made collaboration much smoother between developers and support teams.

One feature I especially value is the version history. It lets us track documentation changes over time and quickly restore earlier versions when deployment procedures or configurations are updated incorrectly. That adds an extra layer of reliability and accountability, which is important in fast-moving projects.

The collaborative editing has also improved productivity, since multiple team members can work on the same document at the same time without creating duplicate pages or ending up with conflicting versions. This is particularly useful during production releases or project migrations, when documentation tends to change frequently.

I also appreciate the built-in templates, which help standardize technical documentation across the team. Using structured templates for deployment guides, runbooks, and technical notes reduces the effort of starting from scratch and keeps information organized and easier to navigate.

Overall, Confluence has become an important part of our internal knowledge-sharing process, and it has helped improve documentation consistency and accessibility within the team.

What do you like best about the product?

It’s easy to use for documentation and sharing with the team. It supports tables and images, and the integration with Jira is seamless, which makes it especially helpful for engineering.

What do you dislike about the product?

Sometimes it takes a long time to load, especially the side navigation. Still no AI help in writing.

What problems is the product solving and how is that benefiting you?

Sharing documentation with the team has been straightforward and helpful.