Atlassian Confluence Reviews

The company needed a tool that project managers put their plans, documentation, and everything related to project management into, including milestones that are not available on Jira. They have to use both this and Jira in order to give a full report to management.

When you're working with Agile, you can't go through from one sprint to another without having a good burndown chart. 

I love the reports and the Confluence board. 

The search functionality is great. 

For me, the initial setup is easy. 

The solution is scalable.

It's a stable product. 

I have a problem with the burndown chart, for example, if I put a time only on the estimation block, it'll not show on the burndown chart. It has to be the points.

I'd like to see better reporting.

The UX is a little bit all over the place. From my experience, people really find it very hard to cope with Jira when they start using that.

The setup could be streamlined further. 

I've used the solution for about 12 years. 

The stability is great. There are no bugs or glitches. 

The product scales well. 

We started at 100 users and have since scaled to 300 users. We will continue to increase usage. 

We previously used a local tool. We needed something better for handling project management. 

The implementation process is easy for me. People sometimes find it easy and yet there is room for improvement in the process. 

We advised a third party on how our workflows needed to be implemented and they implemented them on the cloud. Then they moved the project to our cloud and set it as a base for everything there. It was actually really smooth. It didn't take too much time.

The full implementation strategy took two months. 

There was a little bit of complication from the bank side. We have a lot of security, unblocked IPS, et cetera. The two months weren't the full implementation time. We had areas that were blocked due to our security control. A couple of times we remained blocked for one week. I want to say the ideal time for the implementation was one month and a week. For us, of course, it took longer. 

We had five people in total ding the deployment. There were three from our side and two from the third party. 

I'd rate the entire process a three out of five in terms of the ease of implementation. 

We have a contract for handling maintenance. The vendor partners are handling it. 

A third-party handled the implementation process. 

I can't speak to the exact cost of the solution. 

We are users and work directly with a vendor partner. 

We are using the latest version of the solution. 

I'd rate the solution nine out of ten. I love Confluence. I'd recommend it to other users. People should try it out. It would be very helpful. 

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.

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.

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.

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.

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 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. 

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.

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.