Confluence
AtlassianReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
4,079 reviews
from
External reviews are not included in the AWS star rating for the product.
Flexible cool collaboration software program
What do you like best about the product?
Creative templates for all your Agile and other projects plus ability to purchase add-ons.
What do you dislike about the product?
Some training is required if you are used to only doing share point based work
What problems is the product solving and how is that benefiting you?
Collaboratively track requirements and projects artifacts for Agile projects between Jira.
Recommendations to others considering the product:
Do keep add-on from Atlassian marketplace in your budget in mind as you can really use some of the add-on to make it all come together. They do have lots free add-on in Atlassian marketplace to try out too!
REVIEW ON CONFLUENCE.
What do you like best about the product?
Confluence is a very good documentation platform that offers users a great way to manage your documents centered on task projects including section graphs because of its convenient-to-use interface including format syntax.
What do you dislike about the product?
A confluence is an indispensable tool for our process at the present and no downsides found presently.
What problems is the product solving and how is that benefiting you?
It gives us the means to swap, without any further effort, with our clients some of the same documentation and belongings. The advance authorization systems enable you to decide which people have access to which files and its simplicity enables fast publication and dissemination.
Good application/tool for documentation and projects tracking.
What do you like best about the product?
The Space thing is a very good option in Confluence. Also, it's connected with the Jira application so you can literally bring all your EPIC/Stories and create a project under a space and share it with the team (business users/shareholders/dev team.
What do you dislike about the product?
I think the GUI should be more simple like JIra app, it's kind of bit complicated right now. Like permission changes for a profile or updating user permissions.
What problems is the product solving and how is that benefiting you?
Taking care of documentation. I really like the option that the team can create space and share it with the team and watchers/viewers of the page or space can get a notification if someone edit or update the page.
Recommendations to others considering the product:
I dont have much recommendations but it would be easier for administrator if chaning permissions for user are easier and the gui itself is kind of harder than jira app other than that i pretty much like this application
Confluence Cloud: The good, the bad, and the terrible
What do you like best about the product?
If it's 2020 and you're looking for a company wiki tool, you could do a lot worse than taking the free version of Atlassian Confluence Cloud for a test drive to see if it suits your needs.
Bear in mind, however, that you'll want to disregard every review submitted prior to 2020 because Atlassian is replacing what it now regards as its "legacy" Confluence Cloud wiki product with something altogether different—albeit with the same name and similar interface.
There used to be a lot to like about Confluence Cloud—truly there was. The approach to documentation collaboration and version history is excellent. However, as a long-term user, what gives me grave cause for concern is how Atlassian has decided to strip out parts of the product it no longer wishes to support, leaving heavily invested customers facing extraordinary uncertainty over their suddenly invalidated business solutions. In fairly short order, customer content is being rendered incompatible. That's the downside of investing in a Cloud solution, basically; it may disappear or be undesirably amended without redress.
Bear in mind, however, that you'll want to disregard every review submitted prior to 2020 because Atlassian is replacing what it now regards as its "legacy" Confluence Cloud wiki product with something altogether different—albeit with the same name and similar interface.
There used to be a lot to like about Confluence Cloud—truly there was. The approach to documentation collaboration and version history is excellent. However, as a long-term user, what gives me grave cause for concern is how Atlassian has decided to strip out parts of the product it no longer wishes to support, leaving heavily invested customers facing extraordinary uncertainty over their suddenly invalidated business solutions. In fairly short order, customer content is being rendered incompatible. That's the downside of investing in a Cloud solution, basically; it may disappear or be undesirably amended without redress.
What do you dislike about the product?
To be fair, it's possible you can live without some key elements of wiki functionality that Atlassian has decided to do away with. And who's to say you won't mind some of the surprising bugs making their debut in the basic feature set—bugs that Atlassian staff have recorded in their ticketing system as being on short- or long-term backlog for an indefinite period. You may even be content with key omissions in functionality being assigned a status of "gathering interest" because insufficient numbers of users have realised they must complain en masse for any action to be taken. None of these grievances should put you off, however, because they simply reflect a point in time—and that situation is subject to change.
You should, however, assess for yourself whether Atlassian is taking its user base for granted or possibly even treating it with contempt. Only you can decide whether you find it acceptable for a company to withdraw a product in which many of its customers are deeply invested—having amassed huge volumes of content—only to replace it with an inferior product that is substantively incompatible with existing material. And if they're willing to do it once, how long will it be before they do it again?
You should, however, assess for yourself whether Atlassian is taking its user base for granted or possibly even treating it with contempt. Only you can decide whether you find it acceptable for a company to withdraw a product in which many of its customers are deeply invested—having amassed huge volumes of content—only to replace it with an inferior product that is substantively incompatible with existing material. And if they're willing to do it once, how long will it be before they do it again?
What problems is the product solving and how is that benefiting you?
For many years, we have been using Confluence Cloud to store both our internal and client-facing documentation. For our branded material, the customisable PDF-export functionality has accommodated our need to produce consistently formatted professional output.
Sadly, the introduction of the new editor (with its reduced functionality set) has negatively impacted our ability to output content to a professional standard. We are relieved that we haven't yet lost access to the "legacy" editor, so we are able to continue producing acceptable output. If/when that access is withdrawn, however, and if the new editor remains inadequate, we will have no other option than to consider an alternative product.
Sadly, the introduction of the new editor (with its reduced functionality set) has negatively impacted our ability to output content to a professional standard. We are relieved that we haven't yet lost access to the "legacy" editor, so we are able to continue producing acceptable output. If/when that access is withdrawn, however, and if the new editor remains inadequate, we will have no other option than to consider an alternative product.
Recommendations to others considering the product:
Be sure to consider the merits of Atlassian's huge, "award winning" user community where everyone is free to air their joys and delights. And please remember that you will be required to play by the Atlassian community rules. Basically, you may submit any number of posts expressing product satisfaction or offers to help other users find workarounds to unaddressed and inexplicably long-term bugs. In short, you may praise the product as much as you wish. Do not, however, under any circumstances voice your professional frustrations or question the motives of Atlassian decision makers. If you do so, you will put yourself at risk of having your access summarily revoked.
When you submit a bug report (which I have done many times), you'll receive relatively swift assistance from a helpful support person. They will check the issue, confirm the bug, and create a separate Atlassian bug ticket (known as a Jira issue) for internal review. The customer bug report will then be marked as resolved because it has been passed on successfully by the support person who is unable to help further (even though the actual issue may never be addressed by the developers), and you'll be asked to review the way your report was handled—which has nothing to do with the actual bug. If you believe that's reasonable, it's all good. Atlassian counts you as yet another satisfied customer. Sure, the bug remains unaddressed, but that's a mere technicality.
So go right ahead. There's much to like, but don't say you weren't warned about the other stuff.
When you submit a bug report (which I have done many times), you'll receive relatively swift assistance from a helpful support person. They will check the issue, confirm the bug, and create a separate Atlassian bug ticket (known as a Jira issue) for internal review. The customer bug report will then be marked as resolved because it has been passed on successfully by the support person who is unable to help further (even though the actual issue may never be addressed by the developers), and you'll be asked to review the way your report was handled—which has nothing to do with the actual bug. If you believe that's reasonable, it's all good. Atlassian counts you as yet another satisfied customer. Sure, the bug remains unaddressed, but that's a mere technicality.
So go right ahead. There's much to like, but don't say you weren't warned about the other stuff.
Review of Confluence
What do you like best about the product?
I like how easy it is to use it. There's many ways to break up the page to tailor your individual need. I also like how it ties in JIRA well and you can link JIRA issues into your Confluence pages.
What do you dislike about the product?
It's not quite as easy to use as Google docs. The formatting options are quite limited.
What problems is the product solving and how is that benefiting you?
Confluence is our database for any relevant documentation. It's a great place to store and update important team information that we can all easily utilize.
A very nice, easy to use, searchable wiki-style documentation system.
What do you like best about the product?
Documentation is easily searchable, even if you don't know the document's title.
Users creating documentation don't need to know any markup languages.
AD/LDAP integration and permissions structures are top notch.
Users creating documentation don't need to know any markup languages.
AD/LDAP integration and permissions structures are top notch.
What do you dislike about the product?
Based on Java and Tomcat. This requires more resources than other solutions, and administrative tasks like SSL termination are needlessly difficult. Newer versions are released as containers which helps mitigate this.
What problems is the product solving and how is that benefiting you?
IT documentation is being centralized in Confluence. It's much easier to search and find what you are looking for. Documents are meant to be read online (it is 2020 after all) and not printed out like MS Office.
Recommendations to others considering the product:
Give the free version a try. You will probably end up keeping it.
The visual collaboration system that often works well
What do you like best about the product?
There are many varieties of layout templates for Confluence. We can use it for our primary departmental business activities or more miscellaneous needs we have for company-wide events. The designs of many of the project templates are often makes it easy to see and digest the information. We can add text, grids and graphics to help organize our information in a way that can boost engagement.
What do you dislike about the product?
I think Confluence has mostly worked well but it's not really a collaboration system that can be used for deeper project management needs with layered activities and dependencies.
What problems is the product solving and how is that benefiting you?
Confluence has helps for team members to plot out project activities, lay out event agendas, and to generally list ideas that each member can comment on. We can have detailed discussions that are backed with resources we can attach to the project. We don't have to meet at a set time as much since we can all log in and interact at any time.
Recommendations to others considering the product:
I'd just try to search for a project template that closely meets your project needs as much as possible to avoid having to fiddle around too much with the layout.
The best workflow tool for a product development company
What do you like best about the product?
I have explored Confluence on my own. Designed the workflow for our documentation structure and designed it in such a way that it falls into our document development life cycle process. The best part about Confluence is it's very much user friendly and easy to learn. We had a discussion group where questions come to us go with a positive answer. Our business analysts are quite happy once they got used to Confluence's workflow. Write, review, publish that's the goal and its as easy as our day to day work.
I personally liked it, what about you?
I personally liked it, what about you?
What do you dislike about the product?
I personally do not have any dislike for this product.
What problems is the product solving and how is that benefiting you?
The problem with our system was to define a workflow to suit our requirement which Confluence has sort out. Moreover it made our life easy, when the work is done we get the notification to move it for further action. Instead of complications it made our life easy.
Recommendations to others considering the product:
Its easy to use. You can go for it if you are looking for a proper workflow tool.
Arrogant customer service - they don't listen
What do you like best about the product?
New editor is pretty slick and fast for basic pages
What do you dislike about the product?
A lot of functionality has been removed from the editor. If you're making complex documentation pages, it's not a good choice.
The product management team come across as aloof and uncaring. Have a look at their comments (or lack thereof) in this page: https://community.atlassian.com/t5/Confluence-articles/2019-All-Wrap-ped-Up-Like-a-Present/ba-p/1235288
The product management team come across as aloof and uncaring. Have a look at their comments (or lack thereof) in this page: https://community.atlassian.com/t5/Confluence-articles/2019-All-Wrap-ped-Up-Like-a-Present/ba-p/1235288
What problems is the product solving and how is that benefiting you?
Team documentation
Recommendations to others considering the product:
Don't use it. Find another solution where the product managers actually care about users.
Used to be good, but now most of the functionality has been removed.
What do you like best about the product?
I used to love Confluence, I wrote most of my pages with wiki markup, but now I'm constantly finding that I just can't do things that were simple in the past.
What do you dislike about the product?
Markup support has been removed
No longer possible to resize tables
Code macro has been removed and replaced with a cutdown version - code snipits
Can't indent text anymore
Have to publish the page before you can put in a link to a heading
The link functionality is greatly reduced and much harder to use
No longer possible to resize tables
Code macro has been removed and replaced with a cutdown version - code snipits
Can't indent text anymore
Have to publish the page before you can put in a link to a heading
The link functionality is greatly reduced and much harder to use
What problems is the product solving and how is that benefiting you?
We use confluence for our online documentation, but we are storing more and more in sharepoint now to to the loss of functionality in Confluence
showing 1,191 - 1,200