Atlassian Confluence Reviews

We are conducting all our project management using Atlassian tools. We use Atlassian Confluence for task management, reporting, visualization of tasks, and reviewing the progress of tickets and work.

I use Atlassian Confluence for task management and other project management tasks, such as reporting, visualization of tasks, tracking the progress of tickets, and understanding how work is progressing. Confluence is integrated with Jira.

Currently, I have no suggestions for improvements. There are no issues with stability or downtime with Atlassian Confluence.

I have been using Atlassian Confluence for five years.

No stability issues have occurred with Atlassian Confluence.

The Atlassian technical support team is reachable through different platforms, and I would rate them seven or eight out of ten.

Positive

There are many options, but I haven't tried other tools for comparison.

Deploying Atlassian Confluence is not inherently difficult, but it does take time if I am unfamiliar with the tool. It might take one or two weeks maximum.

Money is a factor because Atlassian Confluence is not free. I need to purchase extra components when adding new projects or employees.

I have not tried other tools, and therefore have no comparison.

I would rate Atlassian Confluence seven out of ten. Since I work closely with Jira, I use Confluence mainly because of how well it integrates with Jira.

We are using Jira as an asset management and ticketing system along with Confluence. We have significant portions of the Atlassian system implemented.

Atlassian Confluence is used as a Wiki for Jira tickets. We maintain software and hardware evaluations, project documentation, and related materials in Confluence.

I have used ServiceNow in the past, but it serves a different purpose. It was used for technical documentation, billing, and monitoring, so the usage cases are not truly comparable.

The linkage between the different Atlassian products is what I find most valuable. You can easily link Atlassian Confluence into a Jira ticket, which allows for a quick overview when you are in the ticket system and the ability to quickly dive deeper into the Wiki directly.

Athlassian Confluence certainly does not save me money with the license fee involved. However, I see it more as a collaboration tool where you have the ability to manage access. Since we have many external companies involved, they have their own areas within Atlassian Confluence, and you have the ability to structure everything very effectively. I do want my people to learn how to structure the tool properly. The danger I see is that when you have several departments, you sometimes get repetition because each team manages their own area within the tool independently. Sometimes information gets lost because of this. That is the only negative aspect I currently see.

Much of the room for improvement lies not with the tool itself but with how people are using it. In many cases where we have had issues, it has been based on the lack of structure. The company using Atlassian Confluence needs to have a very clear structure for where information will be organized. As I mentioned, we have subsections that contain the same information, which makes searching problematic. When you search for a project, you suddenly get fifteen pages about the same project, which does not make sense. A lot of these issues lie with the site owner who needs to be more structured in their usage of the tool.

Atlassian Confluence is used during meetings, especially during product evaluations where we work on collaborative projects. We also use it as a note dashboard for brainstorming and similar activities.

We have a team that is creating templates for ourselves, and we are not using anything external for that purpose.

I changed companies, so we were using different solutions before. We are using Fortinet nowadays.

The cloud version is rather simple to set up. The on-premise version is more complicated because you need to configure access rights with our SSO system, which is rather complicated on the on-premises version.

We have a local vendor here in Austria who handles the implementation for us.

We are not currently using Atlassian Confluence directly for analytical purposes. We use Power BI for that instead. I would rate this product nine out of ten.

I have been dealing with Atlassian Confluence for approximately twelve to thirteen years.

The most valuable features of Atlassian Confluence are its overall document editing and ease of use. When comparing it to other solutions such as Microsoft SharePoint or other wiki tools, some are far ahead or far behind on ease of use when you start to edit and publish a document. That is the key thing, and then I can also build the structure of pages and easily manage these spaces and control access rights.

The impact of real-time collaborative editing on my team's project workflows is not particularly useful. It is handy when, for example, we are taking meeting minutes, as we can together modify and type in the minutes. However, in the normal case, such as when I have been using it for product documentation or requirement gathering, it is normally one person doing it at one time. It is a good feature, but it is not really at the top of my list.

What I would like to improve in the product is definitely the Jira integration. It is hard to tell which product is lagging or lacking because I can usually find a feature on the Marketplace if I am missing something. The Atlassian approach of keeping the base product really stable, simple, and easy to use is beneficial. I think that is a good comparison to IBM, where all possible features are built into the UI, making it super complex with so many buttons and options.

For additional features I would like to see in the future, I would improve the requirements management setup so that I can use Atlassian Confluence and Jira together in an efficient way. I would also build better status monitoring or more granularity on the actions that I can perform.

I have experience with Atlassian Confluence, and I have very little experience with Jira Portfolio, which I think never really took off, as I do not know any company using it. I have been using mostly Jira and a range of plugins and Atlassian Confluence.

Regarding customizable templates, I find that they are quite good now, especially in the cloud, as they have these product development templates and team templates. I should use them more, and I normally tell customers to take advantage of those. I can modify and create my own templates in Atlassian Confluence, and that is what we do quite a lot in our consultancy work.

Regarding analytics features, it just depends on the use. The pure analytics regarding who has been using what and when is not that useful. However, if you are in a regulated company, you can extend those with some plugins to get highly monitored and high-level analytics. I think it is good that they are extendable.

Concerning the integration capabilities of Atlassian Confluence with Jira, I find it surprisingly simple, meaning it does not really have powerful features in it, but it is easy to set up. When I know what I am doing, such as when I build a project status page, I need to include many Jira widgets or these macros in the page. Once I get that done, it is really handy, but I would say it is a little hard to use in the beginning to get some real benefit out of it. I would say it is lagging behind what we would consider a company such as Atlassian, which has been developing these two products for twenty years.

I would rate this review nine out of ten.

Mainly, usage involves multiple activities that I do, like updating the entire team structure. There is technical documentation, holiday details, and several segments. One important segment is technical documentation related to the project activities, which all developers, testers, and the VA must follow. 

It is a common repository for them, providing only read access rather than write access. Apart from that, there is a team structure aspect—about who hires the team, their IDs, single sign-on (SSO), joining details, and when their SSO will expire. 

This information is mainly for me and my upper-level boss. You can get all the details if you want to know how many associates are working on this particular project. It's a summary, with a chart that gives an overview of the resources, so that is another segment.

Copying another page and providing an option to edit everything is valuable. Specifically, when I want to edit something, it offers that option immediately. I can tap on it or mouse over it, and you have immediate access. 

The new UI, which launched six to eight months ago, includes many other features. I find the editing option straightforward and quick. It is a feature I like most and frequently use. 

Additionally, this tool provides a single repository for interacting with the entire team. It's accessible from anywhere, and people from different regions, like India or Germany, can use it in their own time zones. It's not only a time-saving solution but also a helpful repository.

There is a holiday calendar, however, I need to install an app or add something to it. The add-on feature is not readily available or well-documented. Guidance on this should be available in a forum. 

Recently, I used a feature in another tool—perhaps GitHub—where it helped prepare a chart. It involved listing resources, like having fifteen people in the X team, ten in the Y team, and seven in the Z team. It created a bar chart showing these numbers. This chart used AI to offer users the option to create it based on the data. It was then created on a separate page and made available.

I'd rate scalability eight out of ten.

In terms of support, I haven't encountered issues requiring support. I usually search on YouTube or different forums if needed. Primarily, there is not much I need from support. I would categorize it as not applicable. As for competitors, I haven't found any tool similar to this one, so I would say it is currently the best in the market.

Neutral

I am familiar with this tool, so for me, the initial setup is simple. I don't find it complex. Even companies are getting licenses for it, so we use our login and admin users. In terms of setup, I don't encounter any difficulty. It is very simple with no complexity.

The overall product rating is eight out of ten.

I use Atlassian Confluence because it's a good place for central documentation. It ties in quite well with Jira for our task tracking. For the bigger features we're working on, we can build our documentation in Atlassian Confluence and then link Jira tickets to that documentation, our release notes, and anything similar.

We only work with Jira and Atlassian Confluence at the moment, as we tried using Jira Product Discovery, but it didn't provide what we needed.

One of the best features of Atlassian Confluence is that it integrates really well with Jira, and it's easy to use. When creating a folder structure or a page in Atlassian Confluence, it's very easy to add tables, add other documents, and tag people. It's very fluent, and the UI is very easy to use.

I haven't seen an ROI from this tool, though I can say it's saving us time because we've got everything in one place as opposed to using Google Drive or SharePoint. However, I'm not aware of any specifics around time saving.

There's room for improvement in the way folders are structured in Atlassian Confluence. Sometimes it's frustrating when we have two documents that we want to have the same name. For instance, we might have two different products with a release going out on the same day, and we might want to label those documents with the same title but in different subfolders. However, it's difficult to provide specifics of what could be better.

I have approximately two years of experience with Atlassian Confluence.

I believe it is a stable solution.

I believe Atlassian Confluence is a scalable solution.

I have never had to reach out to customer support from Atlassian, as I've never had any issues. I could rate it a 10 because I've never encountered any problems.

Positive

We used to use Google Drive for the majority of our documentation before switching to Atlassian Confluence.

We moved from Google Drive to Atlassian Confluence partially because it integrates with Jira, which we use for task management for our development teams. The functionality in Atlassian Confluence is better. The documents you can create have more options, and you can customize those documents more extensively, whereas with Google Drive, you've just got either Slides, Google Sheets, or Google Docs. While they're good, Atlassian Confluence is much better for putting together more complex documents.

I have experience working with these solutions as I work for a company that provides similar solutions. I was doing competitor research to see what was available online. I found PeerSpot on Google and did some research there.

I have experience working with other tools, as I use Jira daily. We only work with Jira and Atlassian Confluence at the moment.

Regarding analytics, we don't really use them in Atlassian Confluence specifically; we more use analytics in Jira for our task tracking and team work. For us, Atlassian Confluence is more just a place to put all our documents, features, and processes in a structured way.

We haven't used real-time collaborative editing as we're a relatively small team. We tend to just talk to each other, either on the phone or in the office.

I would rate Atlassian Confluence an eight out of ten overall.

I would prefer to remain anonymous for both my personal name and company name.

At the moment, I think real-time editing is very helpful. Multiple teams can engage in real-time editing, commenting, and notifications. This feature is beneficial because I can share documents with others, allowing two or three people to seamlessly edit documents. 

Commenting is a good feature as well, as it enables team collaboration on different tasks. The pages in content are quite impressive, equipped with multiple features. Users can create tables and directly pull all Jira tickets into a Tableau format. This simplifies the process, as we don't need to spend time creating tables in Google Docs or Word and manually linking Jira tickets. 

Confluence is seamlessly integrated with our Jira, making it easy to link tickets and access complete descriptions.

The software does not currently have any kind of AI integration. Given that many platforms are now incorporating AI, I believe Confluence should also consider AI integration. 

Additionally, a few more editing features could be added. Compared to a Word document, there are some limitations in Confluence. While we use Confluence mainly as a repository, more options similar to those available in Word or Google Docs in terms of formatting and other features could enhance its functionality.

I have been using this solution for more than a year.

We have never faced any downtime. Working in the Indian time zone might contribute to this, as scheduled maintenance messages from Jira typically occur on Saturdays and Sundays. We currently have no downtime issues.

We have a dedicated Jira admin team to handle issues, so we do not deal directly with customer service. This team manages all queries and uses various plugins, such as Tempo for time tracking. We rely on our own admin team to address all Jira-related concerns and questions.

Positive

With Atlassian, the costs are reasonable. Although higher than before when we used multiple platforms and licenses, having a collaborative platform like this is advantageous. It streamlines license management and renewal processes, which can otherwise lead to complications or lapses in access.

I rate this solution a nine out of ten. 

Having one license for everything simplifies renewals, and establishing our own Jira admin team has made documentation more efficient. Compared to other bug-tracking and project management tools I've used, Jira offers significant value.

I use Atlassian Confluence for documentation purposes. It is utilized for storing project data, sharing tickets through Jira to Confluence, and measuring documentation for every step of a project, much like a Wikipedia-style tag. Everything is noted in a step-by-step process on the Confluence pages.

Confluence helps save time and facilitates easy data sharing among team members. It allows us to create spaces for meeting notes that can be shared with other team members without reaching out individually.

The macros feature in Confluence is quite valuable. It allows the creation of tables, calendars, and the integration of hyperlinks with ease.

There is a significant difference between the data center version and the cloud version of Confluence. Providing the same features in both versions would be beneficial. 

Additionally, there is no functionality in Confluence to have a team title as a home page header and footer on each page export, which is something I've requested from Atlassian.

I have been working with Confluence for more than six years.

Stability depends on the setup. If you have good hardware and availability servers, Confluence is usually available continuously. The stability is primarily determined by the server and hardware configuration.

Scalability also depends on how you set up Confluence. It is easy to scale and expand the product.

If you take the premium support from Atlassian, they reach out within one hour. Otherwise, normal support takes one to two days.

Positive

The initial setup is very simple. Migrating from other tools to Confluence, or from cloud to the data center, is easy.

We didn't require any third-party consultants for the setup. We established this in-house.

Atlassian products, including Confluence, have yearly price increases of approximately five to twenty percent.

I'd rate the solution nine out of ten.

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.

I use the solution for my company's customers, who are mainly in the knowledge management system. The tool is also useful to deal with any kind of project documentation or team documentation.

On the reporting front, if Atlassian can bring in more Jira inside Confluence, it would be good since it fails to do so currently. When it comes to the UI with respect to the functionalities, Confluence cannot replace Microsoft Word at the moment, so even though it can be used as a document management system, it is not meant for document creation, which adds a lot of limitations to it. Users will not be able to provide Confluence as a standard document. The aforementioned aspects are areas where Atlassian can have a look at and slightly refine the product.

In terms of reporting, the tool provides a very limited aspect when it comes to its ability to allow users to pull data from Jira and give a report. Reporting works in many ways when you want to present something with respect to a project or status to C-level professionals. Putting reports to be presented to C-level professionals in Jira is a very tough task, but instead, if you can make it inside of it as a document, then it would be easier, printable, and convertible into PDF, or else, you can embed it elsewhere as well, helping provide more clarity to users on what exactly is happening, after which it can provide real-time reporting of the project.

I have been using Atlassian Confluence for six years. I am a user of the tool. My company also has a partnership with Bitbucket.

Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution a ten out of ten.

Around 20 to 30 percent of my company's clients are enterprise-sized businesses, while the rest of our customers consist of medium-sized businesses.

Customer support through Atlassian is good since it offers a ticket-based support system. The product's customer support also does allot the relevant solution engineers when the problem is too technical, or they need an immediate resolution. Atlassian's support is pretty good. I rate the technical support a ten out of ten.

Positive

I rate the setup phase a ten on a scale of one to ten, where ten means that it was a very easy setup process.

The solution is deployed using the cloud services offered by Atlassian. The tool cannot be deployed on an on-premises model.

The solution can be deployed in a matter of minutes. The moment you are okay with the domain and other stuff, it will just take two to three minutes for you to initiate or spin an instance for you.

The product is neither cheap nor expensive, meaning its price falls somewhere in the mid-range zone. I am not sure about the price of the product, but I know that the pricing-related information is available to the public on Atlassian's official website.

The product is mainly used as a knowledge management tool in the service industry, where some service management products are used. The tool is also predominantly used in the IT industry, where there is a need to maintain some documentation and databases.

The tool supports remote team collaboration and communication since it allows us to create team spaces where a team can collaborate to indulge in brainstorming or for any kind of idea-sharing session. The tool also provides the functionality that allows you to collaborate on the same document with other team members simultaneously, and such features help users in co-creating ideas and documents and in reviewing them.

The most useful features of the product for team productivity include areas like whiteboarding, which is a very awesome feature as it allows users to create Jira tickets right from Atlassian Confluence. You can also hold brainstorming sessions in Atlassian Confluence. The anonymous access to pages and its ability to allow you to extend something like your troubleshooting article that provides guidance related to your applications or services to the external world without even having the need for Atlassian Confluence is possible since the tool is helpful in areas like page versioning and history feature.

When it comes to the integration capabilities of Atlassian Confluence with other Atlassian products and third-party solutions, Confluence integrates with Atlassian Suite and, most importantly, with Jira Service Management and Jira Software in a pretty straightforward manner. You just need to put your domain URL and basic credentials for Atlassian Confluence's integration features, after which it becomes available for you in Jira as well as in other tools.

I do manage permissions and access control in Confluence for different team numbers in our company. The product's permission schemes are solid and granular, so in our company, we can do it at a space level or at a page level as well as to who can do what kind of activities, and it can be a group-level approval that you can deny it at a user level, making it a helpful product.

Atlassian Confluence can be used to deal with software documentation and even meeting notes, so HR departments can use it for one-to-one discussions. Organizations can use the tool for their 90-day plan and for top priority lists. The tool can be used for brainstorming. The tool can be used in a lot of cases in any organization.

I rate the tool an eight out of ten.

We use Atlassian Confluence for internal communication and documentation for protocols. You can also use the solution for knowledge management and document management because it allows attachments and some descriptions.

Atlassian Confluence is flexible and allows adding different types of context on the page and connecting a hypertext, like a web page, without a source.

Atlassian Confluence is not really a community-friendly solution. If you have a company, you'll have a license for each person, but it does not have such features as commenters. For example, Jira Service Desk has licensed agents and customers who are public and not licensed. Atlassian Confluence has no public type of users who can comment or do any activity without a license.

I have been using Atlassian Confluence for more than ten years.

I rate Atlassian Confluence a nine out of ten for stability.

Around 12 clients are using Atlassian Confluence.

I rate Atlassian Confluence ten out of ten for scalability.

Depending on the system, the solution's initial setup could be easy or complicated. I rate Atlassian Confluence around eight to ten out of ten for the ease of its initial setup.

Atlassian Confluence can be deployed on the public cloud, on-premises, personal servers, and in any infrastructure.

Overall, I rate Atlassian Confluence a nine out of ten.