It is a collaboration tool. All of our company documentation is on Confluence.
I am using its latest version. It is a cloud solution. Atlassian is the cloud provider.
It is a collaboration tool. All of our company documentation is on Confluence.
I am using its latest version. It is a cloud solution. Atlassian is the cloud provider.
It is very useful for companies that want to deploy their documents in a private cloud repository. Companies don't need to store their documents on some servers on their premises. This document collaboration platform makes it flexible to reach your documents at any time. There is no time or location limitation. You can reach your documents whenever you want and wherever you want. For that reason, it is a very useful tool.
Collaboration is most valuable. You can upload or create your documents on Confluence and share them with your team members. Your team members also can share documents.
Confluence can integrate with draw.io and some of the other third-party tools as well. For that reason, it is joyful to use.
It has good integrations, but its integration capabilities can be improved.
They can improve the table feature of Confluence. It is currently not adequate.
I have been using this solution for three months.
It is a stable solution.
It can be used by as many team members as you want to collaborate. It is no problem.
You don't need any technical support. It is easy to use.
It is just for document collaboration. There is no deployment period. You are just creating your documents on Confluence.
I am using the paid version. My company has purchased it for company employees. We are using Confluence as a company. I don't know how much it costs, but its price is good enough. Its price is not so high.
It is a collaboration tool for document development. You can create, improve, and share your documents through Confluence. It is quite an efficient tool to collaborate with your team members. I would strongly recommend it.
I would rate it a nine 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 use the solution for all kinds of documentation that are part of the testing, product, and development phases and for taking meeting notes.
Atlassian Confluence has definitely improved our organization. Before Confluence, we only had documentation on JIRA. Now, the requirements are routinely documented. We use the solution for test planning and documentation-related testing. It is also extremely useful for technical documentation. You can create different spaces for the different teams. Atlassian Confluence has helped the company a lot.
We have found limiting permissions and history very valuable. History tracking is good, and so is commenting and tagging somebody when commenting. Other valuable features include linking Confluence and JIRA and having a Confluence cloud on Slack. The roadmap feature in Confluence is very good.
The comparing history versions feature could be improved. It's messy and not useful. I remember that it was much better initially.
The roadmap feature should be made easier to work with and modify. It's not really scalable. Confluence is hard to work with as well. Specifically, you cannot set the dates or choose shorter periods of time, like one day or two days. It looks a bit messy. I kept getting questions about it, so I added a note advising people not to pay too much attention to the inaccurate dates.
We've been using this solution for more than two years.
The product has really great performance. There are no issues with that at all.
The team more than doubled in the last couple of years, and we didn't have any issues with scalability. It was very smooth.
I never had any problems, so I never had any experience with customer service and support, and I don't believe anybody did, or they would've shared it on the channel.
We previously used JIRA, but it didn't work because the tickets became old, and it wasn't easy to tag where the documentation was. So that's why we switched to Confluence.
There were no other options on the table before we went for Confluence because I wasn't on the committee that selected it. But using JIRA as an adapting product probably made the team choose Confluence faster. And some of the team had used it before. I had used a very simple version around five years before. So I had some experience with it. Of course, in five years, the tool had changed a lot.
Our ROI is more like something that helps us save money and share knowledge when onboarding new people or introducing existing employees to new processes, products and services and planning, but it doesn't really generate revenue. You could say that our ROI from this product is a monetary and quality-of-life improvement.
I would rate Confluence eight on a scale of one to 10.
I'm not sure whether all our applications are available on the same cloud. But one of the clouds we use is AWS. And since the product is on the cloud, we don't usually have any issues. You don't need to maintain it or make backups because you can contact the cloud provider and ask for whatever backup you need if anything is lost.
I never encountered any problem with the solution that required help from support. So I never reported any issue to management, and I don't believe anybody else did, or it would've been shared on the channel.
It took us some time to benefit from Confluence because we had to create a documentation process, which meant adopting a document mindset to get into the habit of documenting, which was a real challenge. At first, we allocated around two hours a day for documenting, which didn't work. But as the QA team grew, we started documenting their processes, which greatly benefited us. We don't benefit much from the dev documentation, but the product and the QA team do. Though it took us a while to get into that state.
I would say we use about 60 percent of the product's features
We currently have more than 30 people using Confluence in our company.
My advice to anyone thinking about using or implementing Confluence is to start small and use it more and more as you get used to it. Start using it as part of your process. It's very important not to dedicate all your resources to it. Start bit by bit, and you'll benefit from it the most. That's how your employees get used to it. Start incorporating it into their processes, but don't enforce it, or it won't work properly. Like everything in life, you have to start small, and as you get used to it, you'll know exactly what you want from it and the best way to get it.
Pioneering team members should start using Confluence, showcasing how it benefits the company. They should encourage colleagues and peers to use it. First users should also add articles and documentation so others can use the tool more easily. Without this encouragement, team members will completely ignore the tool, and it will be put down as lost expenses that didn't benefit the company.
We use this solution to manage the knowledge base within our organization. We're looking to use Confluence for collaboration and data, sharing information internally and externally. Confluence is connected to our JIRA, so we also use it for task management. And vice versa, JIRA can link to the Confluence page. We are customers of Confluence and I'm a data manager.
It's great for us that this is a free format. It's easy to share information with other people and the integration with JIRA is good. The product is getting better all the time with a new template and new functionalities. This is a robust, agile, and reliable tool for collaborating.
The search function is not great. That's one area where we feel that Confluence is lacking. The second issue is that an additional license is required when you are sharing data externally. There are a couple of instances where we've had integration issues with other apps and that needs to be improved. I'd like to see more of a workflow process. For example, an approval process, where you get through one layer and then go to the next layer, like the process that SharePoint has.
I've been using this solution for two years.
The product is becoming more stable and reliable these days, I think. A couple of versions ago we had some issues when a lot of users were updating to the same page or sharing documents. It's much more reliable now and we haven't had any problems in the past six months.
Our company is not that big so we haven't needed to scale.
We deployed in-house.
Licensing is not very expensive. The issue is that engagement with an external party or stakeholder requires the purchase of an additional license. It's the same issue if we have a consultant coming on board and is a pain point for us.
It's important to understand your needs in terms of the number of processes and number of people you need to support in your organizational structure. Implementing up front will likely help in terms of knowing in advance that the product will be supported. Otherwise, there might be a situation where the configuration will need to be changed after the initial setup. Confluence was initially somewhat complex for us. There were a lot of things we needed to consider and configure. Over time as we grow and evolve as a business we're getting more of an understanding of how the solution works and it's getting easier. There's a learning curve.
I rate this solution eight out of 10.
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 document all the processes and flows we are planning to implement on projects. We capture all kinds of documentation.
It's the best application to document all types of information. That's the best part. It's a good product, generally.
The solution is stable.
We can scale it.
Technical support is helpful.
On the cloud, we do not have a source editor if you want to go and validate the watch type of HTML or if you want to pull that HTML content for that cloud of pages. Atlassian needs to provide the source editor or a built-in plugin.
I've been using the solution for more than six years. It's been a while.
The solution is quite stable and reliable. There are no bugs or glitches and it doesn't crash or freeze.
600 people are using the solution currently.
While the solution is scalable, we had an issue with each user. For example, users are not able to log into their applications on the cloud. Only on the cloud do we face this issue.
Technical support has been helpful. We are very satisfied with the level of support they provide.
In terms of the initial setup, we were not able to do it right. Separately, we needed to build our own add-on.
I'm a customer and end-user.
While now we use the Atlassian cloud deployment, it used to be deployed on-premises.
It's a simple application for documentation. New users just need to know how to create the permissions or the pages, the restrictions, or the macros. If they know, that's fine. They can use the Confluence application and they will find it very easy.
I'd rate the solution ten out of ten.
We are using Atlassian Confluence as a repository for files.
The most valuable feature of Atlassian Confluence is the ability to access your files from anywhere.
Atlassian Confluence should improve the interface, it needs to be more user-friendly. It is easy to use, but it could be more intuitive.
I have been using Atlassian Confluence for six months.
Atlassian Confluence is stable.
I have found Atlassian Confluence to be scalable.
We had approximately 25 people using this solution in my organization.
I have not used the support from Atlassian Confluence.
Atlassian Confluence was relatively simple to set up. The time it took was only a few minutes.
My advice to others before using this solution is to look at some tutorials or do a quick workshop to understand how the platform works. They can use a Google search and YouTube to find information.
I rate Atlassian Confluence a six out of ten.
We have a standalone, server-based version. Confluence is installed onsite. Nowadays, they don't provide any standalone versions anymore. They just provide the cloud versions for subscription.
Confluence is easy to use and integrate with other solutions, including social media platforms.
Managing user permissions and credentials could be easier.
I've been using Confluence for about five or six years.
Confluence has average stability.
Confluence's scalability is okay, but you have some performance problems when you're working with too many people.
We have many engineers, so we don't need to contact Atlassian support.
Deploying Confluence is complex. It requires deploying many other libraries. We don't pay for maintenance anymore. We just maintain the solution ourselves.
We buy the solutions through the internet and install them ourselves.
They provide both subscription models, but I don't manage the licensing for our company, so I don't know what it costs.
I rate Atlassian Confluence seven out of 10. I think the on-premise solution we have isn't good for novices. If you don't have a lot of experience, you should try the cloud solution.
My team uses this solution for documentation and collaboration.
The solution is very intuitive and provides excellent content management.
You can easily switch between tools through hyperlinks. It is also well integrated with Jira.
In the next release, I would like to have the ability to import pictures.
I have been using this solution for about six months.
The solution is scalable, we currently have about two hundred users who are senior employees within our IT department.
There is an annual license.
My primary use case is for processes in project documentation.
The best feature is document management.
An area for improvement would be the intuitiveness of using the features, especially if you want to customize. In the next release, I would like to see an instant messaging feature for document collaboration.
I've been using this solution for eight years.
The stability has improved and is now good.
This solution is very scalable.
The initial setup is straightforward, though the time it takes depends on the size of the project.
Atlassian is trying to push the license for their online version, but our customers are not ready for that yet. Its licensing is also quite highly-priced.
I would give this solution a rating of eight out of ten.
