Atlassian Confluence Reviews

One of the valuable features is Confluence and JIRA integration. The most valuable integration feature between JIRA and Confluence was being able to easily link Jira tickets to Confluence pages and vice-versa. They felt quite seamless. This reduced work friction, and prevented jumping between systems. It is simple, but very useful. The more integration the better, such as the integration with Slack.

The tool improved team collaboration around a usable source of truth.

I would like to see an improvement in licensing so I’m not paying for inactive users. Basically, I’d like the “system” to count unique active users for the past month and only charge me for those, rather than me manually assigning licenses to users. That user management/subscriptions management was a bit painful, especially in larger environments.

We have been using this solution on and off for five years.

There were no stability issues.

There were no scalability issues.

Technical support is very good.

We used SharePoint and Wikis. They were hard work and had poor integration.

The initial setup was easy. We used SaaS.

Slowly release to users and add subscriptions. Keep on top of subscribers and remove idle/inactive users.

We did not evaluate other options.

Just do it.

We use this solution for all activities related to the software development lifecycle. We use it starting from product spec and product definition documents and release notes to any customer discussion documents, design or architecture documents.

The ease of use has been one of the most valuable features. It has a very simple wiki. The other salient feature is the search capability and association with Jira, which comes integrated with it that makes it convenient to use.

The user interface is a little bit stale. The file attachments and how they work could be improved. There is also room for improvement when it comes to CDNs. 

I have been using this solution for ten years. 

This is a very stable solution. I would rate it a ten out of ten. 

This is a very scalable solution. I would rate it a ten out of ten.

We have rarely needed any assistance from the support team. When we have needed support, they have been very helpful. 

Positive

The initial setup is very simple.

The Confluence pricing is good. The only challenge we have experienced is with Jira and the add ons we use that need to be paid for separately. 

I would rate this solution a nine out of ten. 

The sharing of information and simple formatting are valuable features. That is, there are no templates, and everything uses one format. This means that people don't need to worry about formatting.

When we have a project that we don't want to share with everybody but want people to know that it exists, there is no way to do this in Confluence. When a project is not shared, people cannot see that it exits.

I've been working with Confluence for eight years. It was initially on-premises, but we moved to the cloud four years ago.

It's stable, and we haven't had any issues at all.

We haven't had any problems with scalability. We have about 300 users.

Some technical support staff are very helpful, but some just send documentation that is not very helpful. I would say that technical support needs improvement.

I didn't do the initial setup, but I think it's pretty easy. When I had to configure a new site, it was very easy.

SharePoint is very confusing, but Atlassian Confluence is very simple. After a couple of days, most people understand how it works, and it's quite simple.

I recommend Confluence to any company that wants to share information inside the company. Confluence is great; it's like a wiki. I would give it an eight out of ten.

We use Confluence to share weekly project information. Everyone in the company uses it daily from project managers down. 

It's easy to search for information.

I'd like to see some improved reporting on usage. 

We have been using Confluence for more than five years.

Confluence is stable. 

Confluence is scalable. Our company has 1,000 employees, and we're growing. It has kept pace with our growth. 

I rate Confluence eight out of 10. I won't rate it nine because my company didn't develop it. If my company had developed it, it would be much better. 

Our company is using Atlassian Confluence for all work related to documentation, calendars, notes, organization of processes, and workflows.

For example, if we have a new process, or we are updating a current process, we use Confluence Project and share it across the entire team. If we need to calendar a vacation, or an event, we use Confluence. The solution is also used to share best practices and release notes relating to the product.

The solution is valuable based on our company policy. It is easy to use. The interface is basic, with everything linkable. We also use JIRA, so Confluence can link any ticket or task from JIRA to be included on the Confluence page.

The way Atlassian Confluence handles tickets could be improved. This process should be easier, more flexible and more useable, such as the ease of creating a table. 

I have been working with Atlassian Confluence for two years.

The product is stable. 

Atlassian Confluence is a scalable tool. We use the solution across lots of teams, not only on-premise but through remote access. We currently have approximately 100 users in the organization. 

Anytime we need to update or add something, we reach out to our administration team. That team can contact the maintenance team for any attention required to fix and close the ticket in a short period of time.

The initial setup of Atlassian Confluence is straightforward. 

I would recommend Atlassian Confluence to anyone considering the implementation of the solution into their organization.

Overall, I would rate Confluence a seven out of 10.

We use this solution to manage the knowledge base within our organization. We're looking to use Confluence for collaboration and data, sharing information internally and externally. Confluence is connected to our JIRA, so we also use it for task management. And vice versa, JIRA can link to the Confluence page. We are customers of Confluence and I'm a data manager.

It's great for us that this is a free format. It's easy to share information with other people and the integration with JIRA is good. The product is getting better all the time with a new template and new functionalities. This is a robust, agile, and reliable tool for collaborating. 

The search function is not great. That's one area where we feel that Confluence is lacking. The second issue is that an additional license is required when you are sharing data externally. There are a couple of instances where we've had integration issues with other apps and that needs to be improved. I'd like to see more of a workflow process. For example, an approval process, where you get through one layer and then go to the next layer, like the process that SharePoint has. 

I've been using this solution for two years. 

The product is becoming more stable and reliable these days, I think. A couple of versions ago we had some issues when a lot of users were updating to the same page or sharing documents. It's much more reliable now and we haven't had any problems in the past six months. 

Our company is not that big so we haven't needed to scale. 

We deployed in-house. 

Licensing is not very expensive. The issue is that engagement with an external party or stakeholder requires the purchase of an additional license. It's the same issue if we have a consultant coming on board and is a pain point for us.

It's important to understand your needs in terms of the number of processes and number of people you need to support in your organizational structure. Implementing up front will likely help in terms of knowing in advance that the product will be supported. Otherwise, there might be a situation where the configuration will need to be changed after the initial setup. Confluence was initially somewhat complex for us. There were a lot of things we needed to consider and configure. Over time as we grow and evolve as a business we're getting more of an understanding of how the solution works and it's getting easier. There's a learning curve.

I rate this solution eight out of 10. 

We have got our own private Confluence set up. In our department, we use Jira and Confluence a lot. These are our in-house go-to tools for managing the agile ways of working. We sort of follow a bit of both models: traditional and agile. We follow the traditional waterfall model outside of Confluence and Jira, so that's more like requirements, specifications, and documents. There's another team, with which I haven't been that involved, that writes user stories and allocates tasks in Jira. They use it quite heavily.

We use Jira more for agile type processing, like for Kanban boards and all that sort of stuff and allocating work tasks and two-week sprints. It supports the actual agile process. Jira is much more focused on the process of delivery.

It is just the fact that it is a one-stop shop for all project documentation. It is compared to storing things in files and directories and stuff like that. It provides the overall usability and accessibility of many projects and documents in one area. 

It would be good if they can continue working towards making documentation and editing as quick and easy as possible. 

It has got a lot of capability, but I don't know how to use it. I don't find some of the things that intuitive. Sometimes, it doesn't seem obvious to me how to use it, but it is like learning any new tool. You actually need to get trained on the tool to get maximum out of it.

I have been using this solution for the last two to three years.

It is scalable.

We have our own engineers.

The initial setup was straightforward.

I would rate Atlassian Confluence an eight out of ten. It provides everything for our use cases.

• Quick and easy editing/creating of web based content
• Content is easy to format and easy to share: You simply type and save in a web browser
• Atlassian is an AWESOME company
• Confluence is the BEST wiki on the market

• It gives our company a single place to document run books, procedures, and knowledge base articles
• It's quick and easy to edit
• It seamlessly integrates with other tools we use, like JIRA

• Some versions have annoying bugs from time to time. Doesn't all software?
• The interface and functionality is different for users used to legacy content management systems like SharePoint. However, spending a few minutes with Confluence and its intuitive interface will have them creating content quickly.

I also manage a SharePoint team, so I'm not biased. It’s just my opinion based on what I see.

I've used and administered Confluence for the past three years, over five versions. I am about to upgrade to the sixth version.

With earlier versions, such as 5.4.4, we did have stability issues. After upgrading, we've been stable and fast.

Stability issues were caused by an increased user load, i.e., scalability.

Technical support gets a rating of 5/5. We pay for Premier support. It covers ALL Atlassian products. If these products are in any way important to your company, it's worth the cost.

We were using TWiki. We needed an enterprise ready tool instead of freeware.

The setup was straightforward and perfectly documented. Atlassian gives you a step-by-step guide. You would expect nothing less from a documentation platform.

Atlassian is dirt cheap when it comes to enterprise software. I would suggest limiting the number of plugins (a.k.a., add-ons), as they are an extra cost and many times you're dealing with third-party vendors.

At the very least, use the ones that say "Atlassian Verified" and "Supported".

We did not evaluate anything else that I know of.

• Hire someone with experience using Atlassian tools, if possible
• Don't implement organically
• Have a PLAN for how you want your information structured