G2

Sree K.

Software Development Engineer in Test III

Computer Software

Mid-Market (51-1000 emp.)

8/1/2026

"Reliable All-in-One Documentation Hub with Seamless Jira Integration"

5/5

What do you like best about Confluence?

I’ve used Confluence a lot for project documentation, test-related docs, release notes, meeting notes, and sharing technical information with the team. What I like most is that everything stays in one place, so I don’t have to dig through emails or multiple folders just to find an older document.

It also integrates really well with Jira. When I’m looking at a user story or a bug, I can usually jump straight to the related documentation without wasting time. That’s been especially helpful during sprint planning, testing, and production releases.

Another plus is that multiple people can update the same page without ending up with separate versions of the same document. It helps keep information current, and everyone is working from the same source instead of maintaining different copies. Review collected by and hosted on G2.com.

What do you dislike about Confluence?

I don’t have any major issues with it, but when a project has been running for a long time, the amount of documentation can grow pretty large. At that point, finding older pages sometimes takes a bit of digging unless everything is well organized.

Formatting tables or longer documents can also be a little frustrating at times, especially when I’m trying to get everything to line up neatly. It’s not something I run into every day, but I’ve noticed it on a few occasions.

Other than that, it’s been a reliable documentation tool overall. Review collected by and hosted on G2.com.

What problems is Confluence solving and how is that benefiting you?

For me, Confluence solves the challenge of keeping project knowledge in one place. Rather than storing requirements, test documents, meeting notes, API details, release information, and troubleshooting guides across different locations, everything lives in a shared workspace that the team can access.

As a QA engineer, I regularly need to look back at older documentation when I’m testing new features or investigating issues. When everything is written down and easy to find, it’s much simpler to understand the application, and I spend far less time tracking people down or asking around for information.

The biggest benefit is that the whole team works from the same set of documentation. That consistency helps avoid confusion and makes knowledge sharing a lot easier. Review collected by and hosted on G2.com.