Atlassian Confluence Reviews

We use it for our knowledge base and also for internal blogging.

The templates are a valuable feature. You can make templates. There is a space inside where you can create pages. When you use the template, the page auto-generates text and images. You do not have to think about the structure of your page as well, which I think is a very good thing for a user. Because usually when you're in front of a blank page, it can be a bit dreadful to know where to start.

Some macros can be technical, and they are better managed on the Confluence cloud rather than on-premises. For example, when you add an image on the cloud, you can resize it just by using the mouse. This is not the case on-premises yet. You have to write pixels of the size of the image sometimes.

Some of the very old macros are still there, and some of them are technical. It can be hard for users if they are not from an IT background to understand how to use them quickly.

There's a feature that is really helpful that I like, but it is inside the cloud version and not in the on-premises version. It is the inline comment in edit mode. In fact, you can do inline comments on articles and pages on both the cloud and on-premises versions, but when you modify the page on the cloud, you can still see them but in edit mode. When you edit the page, you cannot see them anymore. You need to have two tabs in order to remember what the comments were.

I've been using it for four years.

Stability wise, Confluence is a reliable tool, and as a wiki, it's a good tool. So, there are no known performance issues.

With regard to Confluence on-premises, the performance would obviously depend on the infrastructure and the hardware behind the installation. So, it won't really be linked to the tool.

On the cloud side, the stability is okay as well.

Confluence is scalable on both the cloud and server data center. On the cloud, you can even go up to 10,000 users, which was not the case three or four years ago.

We have nearly 300 users. We do our assignment reports on it, and some use it in sales. Managed services staff use it to share information with clients. It is used by everyone.

The installation is easy, and there's nothing more to do after the installation. It can be ready to use very quickly.

Deployment would probably take a day or two at the most. However, if the client needs advice regarding the structure of the company and how to do the knowledge base, then it can take several days. Usually, this is up to the organization, but as it's really quick to use, you can create whatever you want the day after the installation.

There are some cases where you can go on Confluence as a public site without a license, but you will not have all of the features. You can also have a Confluence site that does not require a license just to read the articles.

When you have Jira Service Management attached to Confluence, then you can go through the portal of Jira Service Management and read the Confluence articles without the license. This is good because when you are in an ITSM environment, you have many customers, and you do not want them to have to pay just to read articles.

Regarding the use of the full features of Confluence, there is a license cost, and it depends on how many users you want.

You should use Atlassian Confluence, but you should not expect it to behave like a document manager. People do ask me what the advantage of Confluence is compared to that of SharePoint, but in fact, this is not the same use case. SharePoint is for storing documents at a place, and Confluence is a wiki.

I would recommend that you go for it but you will need to remember that it's a wiki and is not designed to store documents. It can store documents, but only up to a certain size. Also, it's not meant to be used to store documents.

If you are looking to deploy your organization or your projects inside Confluence, do think about the right structure because it will influence the way your people use it. Think about how to deploy the structure of your projects or your documents inside the Confluence, and do not expect it to be a document manager.

On a scale from one to ten, I would give Atlassian Confluence an eight because it's a great tool. It's a great wiki and is easy to use. It's easy to understand how to use it as well, particularly if you are from an IT background. Someone who is not from an IT background might need some help in the beginning on how to use it. The setup is really easy, and you do not need specific skills to deploy it. However, the comment feature and macros need improvement. It would be nice to have more templates in the future.

I use Atlassian Confluence for all kinds of documentation purposes, such as sharing information about specifications among the group and distributing those documents for review remarks from others. It's a nice way of distributing information between different teams.

Atlassian Confluence's most valuable features are the ease in which you can use the tool, the flexibility in creating folder structures, receiving notifications in case others put remarks on the documents, and working together on documents.

Atlassian Confluence could improve how information is shared outside our company. We had some negative experiences with the rights we have with our information when sharing it within Atlassian Confluence and with other teams outside the company. It's due to the limitations on the rights we have on the export capabilities. We don't have sufficient rights to do so.

In an upcoming release, there should be improvements in the graphical support for drawings. We have some plugins, but it's limited for making drawings within Atlassian Confluence, it's rather difficult. Most of the time we create I create drawings outside Atlassian Confluence and import them as a file. It makes it a bit difficult to update drawings within the solution itself, but it's mostly limited to the plugin support we have internally.

I have been using Atlassian Confluence for approximately five years.

Atlassian Confluence is a highly stable solution. We receive notifications from the vendor if there is maintenance work that is required. The overall stability is good.

The scalability of Atlassian Confluence is very good when I see how many people are using it. There could be up to 1,000 users using the solution. 

I have not needed to use the support from Atlassian Confluence.

The initial setup of Atlassian Confluence is straightforward. It's set up within the company and we ask to create workspaces for ourselves.

We have a site license for Atlassian Confluence and there are some limitations on external users.

I would recommend others to use these solutions. The ease of use and the very short learning curve, make it an ideal tool.

I rate Atlassian Confluence an eight out of ten.

The solution is very simple to collaborate among a large group of people. If you want to create a bit more compelling, nice-looking documents, then it's not ideal, but for the thing we are using it for, it's perfect.

We are a banking institution and use this solution to provide the key technical and functional documentation of the project that we share with our users. I'm the managing partner and we are customers of Atlassian.

The product is quite intuitive and user-friendly. It offers a lot of freedom when drafting directly online, and there are some very nice features to connect with JIRA, for instance. It's helpful that the solution enables documentation of user histories that you are following or tracking in JIRA and links the two. 

The performance could be improved, we sometimes run into difficulties creating tables. 

I've been using this solution for six years. 

The solution is very stable, we've never had a problem. 

The solution is very easy to scale, especially because it's easy to interface with other applications. In my project at the bank we have over 100 users; my client has thousands of users. 

I've never directly contacted Atlassian support because we have our internal IT department. If I have an issue, I raise an internal ticket via ServiceNow and the administrators of the bank take care of things. If necessary, they contact the vendor.

I'm not an administrator but I believe the initial setup is relatively simple. From a user perspective, you can very easily create a dashboard, quick links, and things like that.

This is a very easy cloud-based solution that permits collaborative drafting of documents. We can have several people editing documentation at the same time which simplifies things. It's a good solution for technical and functional documentation.

I rate this solution eight out of 10. 

We use the database for documentation and requirement gathering. So, we document those and create plans or backlogs.

I have actually not used the solution much. I have only used the solution to create pages, and I also used it to document certain requirements.

The interface is good. Usability-wise, the solution is not great. However, I can adjust, and I can work on it.

The solution's user experience needs to be improved. The solution is not very user-friendly. From my perspective, it should be more user-friendly.

In the future, the solution should be able to integrate with other tools. I think it is integrated only with Jira. But there are other tools with which it could also be integrated. We should be able to integrate this tool to get a trace of what information we are gathering. Maybe it is only possible for Jira because it is a Jira product.

I have been using Atlassian Confluence for around a year.

The solution's stability is fine. It automatically saves the data. We don't lose any data even if we don't save it manually. So that way, if something happens to the system, it drops and shuts down, and the data is automatically saved. I rate its stability a nine out of ten.

I didn't face any issues with the scalability. It was very good. I rate its scalability a nine out of ten.

I have not contacted customer support yet as I have not experienced any issues with the solution. I rate the technical support a nine out of ten.

Positive

I don't have any experience with other products. I have used Azure DevOps, but I have not used too many products in this category other than Confluence.

The initial setup was straightforward and not too complex. I rate the setup a seven out of ten. I think the solution was previously deployed on-prem, but now, I think it is on the cloud. I also do not have an idea of how long it took to deploy Atlassian Confluence, as it was done by the backend team and not us.

I don't have an idea about pricing. But I can say that I think it's a good tool for requirement gathering, where you can create backlogs and store or document the data.

The solution may need a web build access code so that it can be used from anywhere. So, once you have access, you can access it from anywhere. And the scalability is also good. So, I can rate the overall product an eight out of ten.

The business analysts use Atlassian Confluence for project documentation and use case stories. I use it primarily for dashboards and KPIs that are set for programs. Most people are comfortable using Atlassian Confluence.

This solution should have customized dashboards that could be built by the user and connect to the data and filtering mechanisms to create dashboards. It will be great for any C-level executive to monitor their KPIs rather than depend on somebody else to create them. So, the dashboards should be improved.

I have been using this solution for about ten years. It is mainly deployed on cloud.

We don't have any issues with stability. We have about 200 users of Atlassian Confluence.

We don't have any experience with technical support.

We have used Zoho, Salesforce, Bamboo and Trello. They almost all work the same because I've seen things done differently. Whether you do project management or documentation, you can choose a solution that's friendly for developers and easy to understand and pick up quickly. I would not say one is better than the other, and each solution has its abilities. Atlassian Confluence seems stable, and we don't have a problem. When dealing with compliance, some of our projects need people and PCI nest compliance, so we also have to look at tools hosted in the manner in which they comply with these standards. IBM products meet some of those requirements.

All things in Atlassian Confluence are set up on cloud. The clients have their administration teams, and they extend an account for our developers, our PAs, and our managers on these platforms. So we don't set up anything. The administration team sets up the Jira accounts on cloud. GitLab and GitHub are set up on-premises while keeping the code version internally. Setup is not a major issue because most of these things are very simple, and you have instructions.

I rate the price an eight out of ten, with ten being a good price and one being a high price. Pricing is not a problem, and you might have other products with lower rates. For bigger companies, price is not a problem because there is always a budget, and the clients fund it. However, if the price gets cheaper, it will be better for users.

I rate this solution a seven out of ten.

We used this solution to create and manage shared documentation, as well as managing the team details and giving visibility of attendance and absence to all team members.

This solution allowed us to easily input details beyond just text, such as creating basic data charts to monitor team performance. 

The document creation features of this solution are also very impressive.

We would like there to be more advanced data manipulation features available in this solution, such as creating more complex charts, and a column freezing option.

We always found this solution to be stable.

I would advise new users of this product, to begin by creating simple documentation, and then move on to using macros and the different features provided, once they know how the solution works.

I would rate this solution as 10 out of 10.

We were developing an eCommerce platform and wanted to capture all of the metrics that were coming across. We chose Confluent, which is a ready-to-use solution. The use case was to track all of the traffic that was coming from across the globe, and create metrics out of it.

We used the solution for monitoring and alerting. It was purely for internal processes so we could monitor the status of services and see if something was happening, like an order not getting through, or the customer dropping, or a problem within the system itself. The ability to capture those kind of metrics helped the business.

The solution does have tons of features, but sometimes we don't want every feature to be there, we just want a basic solution. They don't offer the option to customize the package, so you get everything with the one bundle price. Maybe we're only using 10% of it, but we have to pay for everything. There needs to be a flexible pricing model, where we can pick and choose services and customize our pricing model.

I used this solution for about a year as an integrator for a previous program.

Overall, we had a good experience with this solution. I'm pretty satisfied because we were able to quickly achieve what we wanted to do.

The scalability of the solution is pretty good. I would rate the scalability as a seven or eight out of nine. 

The solution has good support.

We used open source Kafka or other solutions where you can deploy the open source version in your infrastructure and you don't have to pay anything, but you have to manage the solution by yourself.

The initial setup was straightforward and quick. 

We used CodeFish for deployment. 

The pricing depends on traffic, like how much input and output is happening and how many messages you're handling. For example, you have a bundle package that has a limit. If you go beyond that, there's a different price attached to it, but if you are within that limit, it's a fixed price.

Overall, the solution helped us to see where we were going wrong and where we were doing good, and that helped us to make proper decisions.

Confluent is a very good product, but only if you are using it to the fullest. If you want to use all the features offered by Confluent, there's no competitor for that, but if you're only looking for basic capabilities, then I wouldn't suggest Confluent. MSK has less capability as compared to Confluent, but since we were not using all of the capabilities, MSK is cheaper for me because I just want the basic features.

Confluent is a classic product. There's no doubt that they're leading the market and their offerings are excellent. I would rate them as a nine out of ten.

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.