Atlassian Confluence Reviews

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 use Atlassian Confluence for the documentation of the application or applications that we are billing. 

Confluence has other functions. My team uses, Confluence every day, but I am just writing some information there that is used for the entire team and is vital for the entire team. 

We are also writing various kinds of material. It is useful for the team to interact and convey information, as well as to document only the information that we use.

I only use it occasionally to check up on documentation or to compose something. 

That is what I am doing. That is the only thing my team uses, however, we also use Confluence to communicate information to the customer. 

Our Confluence is available to the customer. 

We are working on the release notes, and he can get data or the most recent version via our app.

I work with Confluence, however, I'm not sure what's lacking.

The price could be improved. I have heard that certain adjustments would be made in 2024 and that it will then be more expensive, but I don't know the specifics.

I have been using Atlassian Confluence for one year.

We are using the premium version.

Atlassian Confluence is quite stable. I have not had any problems with the stability.

Atlassian Confluence is scalable, and usable from anywhere, as well as from my phone. There are various Confluence or Jira applications, I can access the data immediately anytime I want.

We have multiple projects and half of my colleagues are using it. We have approximately 25 users in our organization.

We have plans to increase our usage. 

We intend to extend it throughout the entire organization. We want to conduct certain HR initiatives on Jira as well. 

Our HR department may also collaborate with them and Jira. I believe it is a useful tool.

I have not contacted technical support.

I use Jira to manage everything in development, and I also use it because we operate in Scrum.

I also use YouTrack.

We used Word to document everything, but that should be the last THRIVE threaded with SharePoint. But, in my opinion, the ideal way is to use all of Confluence for that.

I was not involved with the initial setup. It was done by my colleague.

We now have two or three persons setting up our administrators, and they are setting up some data and looking after the maintenance.

We have to pay licensing fees.

I would recommend this solution to others who are interested in using it.

I think that it is one of the best products on the market from my experience.

I would rate Atlassian Confluence a nine out of ten.

We use this solution for documentation purposes. It's very tightly integrated with Jira, so we handle project management with Jira and document management with Confluence.

We value the way we can tag documentation to Jira because we can cross-reference a Jira ticket to a Confluence page, and we can also add a Confluence page to a Jira ticket. The way both work together helps us to reduce the duplication of the codes, and if we need to have documentation, we describe it in Confluence and tag the page in the Jira ticket for someone to work on, which reduces the duplication of work.

On each page, we can see the different version updates that have already been done by colleagues. It's auditable, which helps us to figure out what changes have been done at what point. Documentation with an auditing capability helps us to manage the overall documentation effectively.

Nowadays, the standard for documentation for developers is mostly in Markdown, so pretty much everything we can do is in the Markdown language. The support for Confluence to import something that's in Markdown is not that great. Sometimes it's also not that great when it comes to including code snippets or similar things, so I think the couple of improvement areas would be around Markdown support and support for adding code.

As for added features, I would like to see more flexibility in the way we can design a workflow in Confluence, and maybe some templates that we can use based on the purpose of the document. 

I would also like to see more integration with other common application services. Other than draw.io, there is not much integration to other services like Lucidchart or similar services, which are helpful for reporting your documentation with drawings and architecture diagrams. Those improvements would make it a bit more user-friendly.

I have been using this solution for five years now. 

The stability partly depends upon the resources that you allocate for the solution, but it's pretty much been stable for the last couple of years that I've been working with it.

The solution is scalable and it's centrally controlled, and we have a couple of central responsibility roles for adding new users. It's helpful for us on the backend because if we want to provide access to different sets of people, some may need edit access, some may need read-only access, and we utilize those different permissions.

Other than utilizing the public documentation that is available, I haven't reached out to the support team.

I was not very involved in the setup of Confluence, but my understanding is that it was not that difficult.

Confluence might be a burden to small and medium companies, like startups, so I probably would not recommend it to them, but I would definitely recommend it for companies at the enterprise level.

I would rate this solution as an eight out of ten because we found it helpful. It's good if you are in need of long-term documentation of projects, both on the functional side and the technical side, but at the same time, it needs some improvements, like more integration to other solutions. 

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.

We are using it for collaboration, team communication, documentation portal, and sometimes project-related content. We keep the details of the project and related documents.

It is a good collaboration tool. You share the document content and also its history through Atlassian Confluence so that you can trace its development. Also, you can add comments to the project-related items in order to track the history. It has JIRA integration in a way that you can combine the project-related dashboards into one space. This increases the communication between the teams. It is a good way to record know-how basis. You can use it as a know-how base for newcomers to be initiated more easily to the items provided.

It is easy to use and create new page content. It has macros and some stamp dates for your projects. If you would like to make something new that you have not done before, it is usually easy to find out on the internet. There is a lot of information available and the search function is excellent. You can search in different spaces and get answers for items you want to find easily.

I would like to see more macros provided by the company. Currently, those macros require extra cost. Additional free capability for those types of integration or components would be helpful in the existing license.

I have been using Atlassian Confluence for almost four years.

It is very stable. I have not seen any virus interruption or issue related to the stability.

I would say that Atlassian Confluence is scalable we have more than one thousand users.

Currently, I have not contacted technical support.

We implemented it through a third party.

We went with Atlassian Confluence because JIRA had the same type of usage.

If you need to create some teamwork spaces it is very good. I would 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.

We're using Confluence as a document management solution. Confluence includes all our documents internally in the company in regards to policies or how to document or about business requirement documents. Therefore, it's a document management system for us.

Confluence can give you the possibility of installing plugins to meet your different needs and you can cover all your needs. Most of them are free to install.

The initial setup is very easy.

Due to the fact that there are so many diverse plugins available, the solution really isn't missing any features. 

The product is considered expensive. 

In the future, I would like to be able to copy from other documents, local documents on your PC, and paste them into Confluence pages while keeping the formatting. At the moment, you can copy and paste, however, all your formatting disappears. This is one of the features that I would want. 

In terms of the feature for uploading documents, at the moment, when you want to upload documents from your local PC into Confluence, you can do it. However, when you want to make updates on your document, you need to download it from Confluence, make the changes in the document, and then upload it again. Instead of doing this, instead of downloading the document from Confluence, it's better to have the possibility to make your changes in Confluence and open the document in Confluence instead of downloading everything.

I have been using the solution for four years. It's been a while now. 

It's stable. It's a really stable product. There are no bugs or glitches. It doesn't crash or freeze. 

We have 50 people on the solution and we have no plans to increase usage. I can't, therefore, really speak to the scalability potential.

I've never had to reach out to technical support. I can't speak to how helpful or responsive they would be. 

I found the implementation process to be simple and straightforward. It's not complex at all. 

I don't handle the licensing aspects of the product. I'm unsure as to the exact costs. It's my understanding, however, that it is an expensive product. On a scale from one to five, where one is cheap and five is expensive, I'd rate it at a three and a half. 

We're a customer and an end-user.

I'm not sure which version of the solution I am using at this time. 

I'd advise new users to not be scared, to play with anything on it, or create documents and delete documents. It keeps tracking the item version. It keeps a version history so that you can revert all your changes back. Never be scared to play with Confluence.

I'd rate the solution nine out of ten. It's an easy tool to use. It gives you the possibility to integrate it with JIRA. All your documents and business documents can be connected to JIRA. With the versioning available in Confluence, history versioning, if you delete something, you can always find it. If someone changes anything in the document, you can find it from the history. It's a really good product.