Atlassian Confluence Review

This became the primary location where all knowledge documents and other documentation were recorded and held, but JIRA and Confluence connectivity needs to be stabilized.


What is most valuable?

1. Its ability to display data from an excel sheet attached to the page. A simple one line code can do this.

2. Allows markers in the page so that they can be referenced in other pages thereby avoiding duplication.

3. Allows creation of random tables when needed for representation.

4. Allows document attachments to be visible as a link whose display text can be user-defined.

How has it helped my organization?

This became the primary location where all knowledge documents and other documentation were recorded and held. Its ability to allow creation of child pages helped to nest topics within topics

What needs improvement?

1. When excel sheets are added for being displayed, it skips document formats and does not recognize merged cells.

2. Supports only MS office 97-2003 formats. Should also support 2010 formats as its a overhead to convert everytime.

3. JIRA and Confluence connectivity needs to be stabilized. We've faced embarrassing situations with stakeholders when the Confluence pages could not pull the list of JIRAs to be referenced on the page.

For how long have I used the solution?

5 years

What was my experience with deployment of the solution?

Deployment was handled by the client's infrastructure team. I'm unable to comment on this.

What do I think about the stability of the solution?

Yes. JIRA to confluence connectivity was a nagging issue. To circumvent this, we started using JIRA dumps into excel and uploading them to the Confluence page.

What do I think about the scalability of the solution?

None

How are customer service and technical support?

Customer Service:

I'm unable to comment on this.

Technical Support:

I'm unable to comment on this.

Which solution did I use previously and why did I switch?

Confluence was already used as the primary tool for reporting and documentation.

However, there have been Sharepoint based solutions for holding documents and their version which I did not find as user-friendly as Confluence.

The other option, of course, is to maintain your documents in a configuration management tool like Visual Safe Source.

How was the initial setup?

Deployment and setup was handled by the client's infrastructure team. I'm unable to comment on this

What about the implementation team?

Deployment was handled by the client's infrastructure team. I'm unable to comment on this.

What was our ROI?

I'm unable to comment on this.

Which other solutions did I evaluate?

We did not particularly evaluate other tools, but when compared with VSS and Sharepoint based solutions, Confluence would be an easy choice. This depends on what exactly is your purpose of using this tool. My views are based on its use as a tool for documentation and a QA's perspective on it.

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More Atlassian Confluence reviews from users
Add a Comment
Guest