Atlassian Confluence Reviews

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.

Our different business units use it for different purposes. We have analysts, developers, DevOps team members, project managers and product managers using it. All these roles use it for artifacts for the jobs they need to do. 

The best feature is the automatic tagging of information in documents. The automatic algorithm highlights irrelevant information that conflict with the actual documents.

You can add different tables and text and format it for different purposes. The integration with JIRA and other tools is quite useful. The different plugins for different purposes are also great. 

The flexibility and simplicity of this solution could be improved. We would also like the ability to add plugins. 

I have used this solution for eight years.

This is a stable solution. We have not experienced any cases of instability.

You need extra time and money to make it useful for a large number of people.

The initial setup is rather straightforward. 

If you are looking for a simple solution to generate documents and artifacts in one place and a simple tool for rules of privacy of this information, I would recommend Confluence. 

If you have a large number of employees or complex processes, you need to have extra time and money to develop tools for Confluence. It doesn't have a pre-built solution for difficult cases for cross functional teams and connections of subjects.

I would rate this solution a seven out of ten. Confluence is a good collaborative tool for work with artifacts of documents, but it has room for improvement. That's why I would rate it a seven and not eight or nine.

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.

We use Atlassian Confluence for creating different pages, and projects on it.

The most valuable feature of Atlassian Confluence it's very easy to use and there are different options. 

We have to use other applications that make Atlassian Confluence more customized for what you want. They should improve by adding the ability to make more customizations.

In a future release, they could add easy reporting. For example, EZPi can be deployed easily into 

I have used Atlassian Confluence within the last 12 months.

Atlassian Confluence is stable.

We have not had a problem scaling up Atlassian Confluence.

We have approximately 300 people using the solution in my company. We all use it on a daily basis.

I have not used the support from Atlassian Confluence. It is an easy tool to use. You do not need a lot of help, but you do need some training.

The setup of Atlassian Confluence can be difficult and other times easy because if you want to implement something, you need to have your process figured out. You have to understand exactly for what purpose you want to use something. Once you understand that, you have to know how you're going to use it. Not only immediately, but also in the future. Once you have this map, then you will be able to use a tool properly. Otherwise, you will be doing trial and error for a while.

If you want to get Atlassian Confluence up and running, the time is depending on whether you want something simple or customized. However, it can be done within a week and have everything running.

There is a license needed to use Atlassian Confluence.

We are using Atlassian Confluence because we mainly implement Atlassian tools for customers. It is helpful for us to use them to understand our customers' needs if there is a problem.

It is important to know what the client wants to use this solution for. After knowing what they want to use it for I would advise them to use it or not.

I rate Atlassian Confluence a ten out of ten.