Atlassian Confluence Reviews

The most valuable features of Atlassian Confluence are version management and search and linkage to the JIRA tickets. They are integrated very well together. You can have links from many places and can easily jump from one to the other. If you want to find all the information about a topic, you only need to click and you receive the information.

From what I have used of the user interface it is good.

I have been using Atlassian Confluence for approximately a couple of months.

Atlassian Confluence could improve the stability, there are timeouts sometimes.

Atlassian Confluence is scalable.

We have a local vendor that I use for support if I need it.

We used the vendor to implement Atlassian Confluence.

Atlassian Confluence is a good solution, I am not sure of the price but if it is expensive it is worth it. You pay for quality.

I rate Atlassian Confluence a nine out of ten.

It's the knowledge base for our company.

We have project spaces for our customer projects, and the project teams share information about the projects.

We also use it as a wiki for our company.

As for valuable features, the team management features help us to share information very easily.

Also, you can work with multiple people on one document inside the solution.

The scalability for larger companies could be improved.

Atlassian has decided to stop the server edition of Atlassian Confluence. In the future, you can only buy an enterprise installation called Data Center, and you have to pay for a thousand users on up. This means that it will be very expensive. So, small installations will only have the cloud option, but the cloud version of Atlassian Confluence is not as stable as the on-premises version.

It would be good to have more graphical components on dashboards to show table components as graphics, pie charts or bar charts. These are not included at the moment.

I've been using it for the last five years.

The stability of the on-premises version is really good.

The scalability is not so good, but it's enough for us because our company is small. We have 30 users. However, we have customers who have 10,000 people on Confluence, and then it becomes a problem.

I would rate technical support at three on a scale from one to five.

We chose Atlassian Confluence because it is really easy to set up the system and because of the functionality. The system has many good functions, and the UI is really modern and easy to use.

The initial setup is straightforward.

Less than one full-time employee is needed for the maintenance of this solution.

Pricing wise, it ends up being an expensive solution. In the beginning it's cheap, but by the time you have all the functions you need, it turns out to be expensive.

Use the 30 day test period to be sure that you want the system. You should use it and test it during this time and then decide.

At the moment, Atlassian Confluence is the best team product you can buy, and I would rate it at eight on a scale from one to ten.

We are using a lot of Confluence. While we are gathering the requirements from the business for the development, Confluence is used. We are creating project charters there. It covers all the functional requirements including knowledge sharing sessions. Basically, when somebody's leaving or somebody is being hired, everything related to that goes on Confluence. This also includes information, for example, about annual leave information, et cetera. If a person is hired and we need to prepare a KT plan for that. So we prepare a page in Confluence.

We like that it is a complete knowledge base where anyone can go and search for various types of information. Different departments are using it. If I want to search for any information, instead of pulling it from files, we have just added everything on Confluence, which makes it easily searchable.

It's easy to use and you can create all types of pages. 

There are lots of functionalities. You can see statues, who is signed in or not, et cetera. 

When we import the data in Confluence from Word or any other document, the formatting is not correct. When we export the data, more or less, it is fine. Let's say from Confluence to Word or Confluence to PDF, it's okay. Otherwise, we face formatting issues.  

The solution would offer more importing features. 

We have used the solution for 15 years or so.

The solution is very stable. There are no bugs or glitches and it doesn't crash or freeze. 

The scalability is great. If your workload grows, it can easily match it. 

We have 700 to 800 people using the solution right now in our organization. HR, production managers, and more are typically on the solution. Pretty much everyone uses it. 

I haven't had any interactions with technical support. I can't speak to how they are in terms of responsiveness.

My understanding is that the pricing is competitive. I'm not directly involved in the pricing and how it was done. That said, the fact that we have been using it for the last 15 years makes me assume it would be fine for our pocket and reasonably priced. I'd rate the pricing at a three out of five in terms of value for money.

Confluence basically is not a management software. It is just a knowledge base. You can search for whatever is there. You cannot manage a project using Confluence. For that, you would need Jira, not Confluence. 

I would recommend the product. Currently, most companies are using Word documents for creating all requirements. Probably they'll be putting those in, either on SharePoint or somewhere. However, these need to be preserved for the future. This solution helps with that.

Overall, I would rate the solution an eight out of ten.

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. 

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