Atlassian Confluence Reviews

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.

The most valuable feature is the ability to create business collaboration solutions without having an army of IT professionals. We can create web-like interfaces without needing to be an expert in Java, Java scripts, or HTML.

We use the tool to establish a collaboration space across federal agencies, state agencies, and other public stakeholders. We are able to create a simple workflow and have an electronic record of those activities.

The basic improvement needed from my perspective (and it may be more to do with how Office of Management and Budget (OMB) has allowed certain features of Confluence to be used) is the ability to move multiple attachments at a time. I would like to be able to copy a set of pages in Confluence as a template. It would be nice to have better business collaboration examples.

We have used this product for five years.

We had stability issues sometimes, but I am not quite sure where those issues occurred. I don’t know if slowness is occurring on the OMB server end or on my organization's end in terms of network transfer of information. Sometimes the system does not respond as fast as a normal web interface. I am happy, overall, because I understand the power of the collaboration efforts being done. However, I think most people are used to one-way communication when it comes to the internet and they expect the same speed when collaborating from a two-way (or more )perspective.

The system has incredible scalability. I have not used all of the features that OMB provides, but we have an integrated system with:

• Collaboration & Information Sharing
• Data Collection
• Analysis
• Publications
• Specialized Applications
• PaaS
• Records Management
• Publishing
• Business Intelligence
• Workflow
• Web Frameworks
• Common Database
• Identity and Provisioning

I don’t interact with Atalssian directly, but rather through OMB who interacts with Atalssian. OMB is my technical contact and in terms of my use of the system they are fairly responsive. The system is a federal-wide system, in which participating federal agencies pay a fee ($50-200K) to be a member and use it as a shared service. When there are special initiatives, a federal agency may have to pay a little more. When I say a little more, I mean a little more, not huge amounts of money.
.

I used previous systems, such as email, common spaces, CDs, snail mail, and lately, SharePoint (we are still using this as well). These are all painful, unsecure systems and require an IT army.

Before choosing this product, we evaluated SharePoint.

If you want to solve complex problems with a simple solution, then use Confluence and use it to scale to more complicated things as you grow.

We mainly use Confluence for our internal documentation work and to plan new features, design documents, and knowledge transfer documents. Most of the documentation work is done using Confluence. 

We have a separate Confluence space for our team, with public articles about our projects and how to set up our repositories, available for anyone to access. 

Additionally, we maintain private content within the team's Confluence space.

Confluence has significantly improved the productivity of our team. Previously, finding information required asking someone or searching through improperly organized resources. Now, all onboarding documents, knowledge transfer documents, and documents regarding features are within our Confluence space, making it easy to find information as needed.

Confluence is very easy to use and feature-packed. It allows us to design well-organized documents and offers valuable add-ons. Its integration capabilities enable direct linking of pull requests and certain issues across spaces, facilitating easy navigation and enhanced collaborative work.

The discoverability of documents could be improved. In scenarios where documents are managed by another department or we are looking for specific documents, the process could be enhanced for easier discovery.

We have been working with Confluence for about a year.

Confluence is stable, and we haven't experienced any disruptions with their service.

We have not escalated any questions to technical support.

Positive

Before Confluence, we predominantly used SharePoint and Microsoft products. We decided to switch to Confluence as we were already using Jira and Bitbucket, making the transition to Confluence seamless with other Atlassian products.

Properly use the features available in Confluence, such as site spaces and other functionalities.

I'd rate the solution nine out of ten.

Confluence is an important tool for collaboration.

We can implement macros in documents. It is useful for document development. We can collaborate with others. The user management and role-based access management depend on Jira. All Atlassian products rely on Jira on-premise. We can also delete the number of users who can access our documents. Document collaboration is the most valuable aspect of the solution.

Indentation and other basic word processing styles must be improved. However, it is limited to editing HTML.

The tool is stable.

The tool can be deployed on-premise or in the cloud. The setup is straightforward. We have to follow several steps for Linux, but the setup for Windows is quite basic.

I did the deployment myself.

I strongly recommend the product. There is no need for scalability. The product’s collaboration features are very strong. Overall, I rate the product a nine 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 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.