Atlassian Confluence Reviews

I'm using it to handle the projects, the Jira project, and the joint projects, track all reported user stories, tasks, and bugs, and create reports and dashboards.

Handling any case, tracking any challenges, documenting any minutes of meetings, anything related to the process, and so on. So, it's very useful to the team to have everything documented on one platform and easily access it. It positively impacts the team's productivity because we have a reference now for processes, technical issues, and challenges.

Documenting everything related to the project is good for me. It enables me to use rich text to document, insert macros and links, highlight with different colors, and organize pages in a hierarchical way. The linking between Jira and Confluence is useful for me. Most features on Confluence are useful for team collaboration. The well-organized search for pages or documents facilitates collaboration.

I'm facing issues using macros like 'expand'. When editing a page with many iterations, it takes time to scroll down to the last iteration. I want to make the permissions in the calendar feature more manageable. I want to prevent anyone in the team from creating a new event and allow them only to add their vacation, as creating a new event should be an admin permission.

I have been using this solution for around four and a half years.

The solution is stable.

I haven't faced any scalability issues.

Until now, we have not needed to contact Atlassian's support team since we have an admin person handling our internal issues.

Neutral

I'm using Microsoft Azure. I use Atlassian more heavily.

The initial setup was already handled by another team, maybe a technical team.

We started with Atlassian and haven't evaluated other solutions.

I rate it a three out of five. While I see the positive impact on productivity, there are areas that need improvement.

I'd rate the solution six out of ten.

We use it to manage different documentation such as PDFs and PowerPoint. It's similar to Dropbox but is more organized. We have approximately 1,000 users that make use of this solution in our business. 

The customization that Confluence offers is one of its most useful features. You can customise it based on the specific project you are working on. It also supports multiple languages. 

I also like using the web browser version of this solution and the fact that it is easy to search. You are able to see more that ten rows of results. 

We currently only use this solution for retrieving information. In a previous company, I also used it for HR and onboarding. The one way in which this solution could be improved is by offering better design and UI.

I have been using this solution for five years. 

This is a stable solution. I would rate it a ten out of ten for stability. 

This is a scalable solution. It is built on a crop base and so adding additional documents is simple. 

The initial setup is straightforward. 

This is a very expensive solution. 

We compared this solution with Lark and I think Lark is a better option. When using Confluence, you can only search using a search bar. When using Lark, you can search through a messaging bot and everything is translated. For example, Chinese words can be translated into English without requiring AI. 

I would rate this solution a six out of ten. It is one of the most well known solutions but comes at a high price and does not offer the best functionality. 

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. 

I use it for documentation, project reports, and creating a knowledge base. 

It's used for building a knowledge base and providing status updates on tasks.

I don't see many features in the version we use. We do find the ability to build workflow diagrams helpful, but that might be through external modules/plugins.

The diagram tool is a positive addition.

However, the only integration we use is with Jira.

There is room for improvement in maybe the tree structure for articles. If you have a lot of articles, it becomes difficult to navigate. 

Having the ability to control which articles appear in the main tree structure and only linking or hyperlinking to others within specific articles could be an improvement.

I have been using this solution for ten years. 

I would rate the stability a ten out of ten. 

It seems highly scalable. There are 500 end users using this solution. 

We have IT, service desk agents, and regular users across different functions. Everyone is using it. For example, if someone needs to look up documentation or assistance with workflows, they would use Confluence.

It's used alongside Jira. Each team would likely have a Jira code for that purpose.

I've used ClickUp. It's a good tool, especially compared to Jira. Confluence still has room to improve in comparison. We also used a legacy tool called CBQ.

ClickUp is becoming a real competitor to Jira and Confluence because it's an all-in-one tool. You don't need separate licenses for project management and knowledge bases. ClickUp has a more seamless experience.  

I've heard of Asana, but I personally prefer ClickUp. If I were starting a company from scratch, I would consider ClickUp over Jira, Confluence, Trello, etc. It's really user-friendly.

I would recommend using this solution. It's not necessarily better than tools like Asana, but it gets the job done.

Jira and Confluence have strong market presence, and migrating existing systems can be a challenge. 

For new projects, I would certainly recommend considering other options. For established teams, switching tools might not be practical. But if you're starting fresh, explore alternatives and don't just default to Jira and Confluence.

Overall, I would rate the solution a ten out of ten. 

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