G2

sreenivasan p.

Quality Assurance Engineer

Hospital & Health Care

Mid-Market (51-1000 emp.)

9/7/2026

"Turned scattered test docs into a single source of truth"

4.5/5

What do you like best about Confluence?

As a QA engineer, Confluence is where my entire testing workflow lives. What I like best is the Jira integration my test case documents, bug analysis reports, and requirement gap analyses all link directly to the tickets they relate to, and I can embed live Jira issue tables in a page so a feature's test coverage status is always current without manual updates. Page templates are the other big win: I've standardized formats for test plans and PRD review docs, so every feature gets documented the same way and stakeholders know exactly where to find what they need. It also made my own onboarding faster when I joined the existing QA space gave me feature context in days that would otherwise have taken weeks of asking around. Inline comments have quietly become essential too: when I document a requirement gap or an edge case question, product managers respond right on that line, and the decision stays attached to the doc for future reference. Version history has saved me more than once when tracing when and why a requirement changed between releases.And on the rare occasions I've been stuck, Atlassian's documentation and community forums have had an answer every time I've never needed to raise a support ticket for day-to-day usage. Review collected by and hosted on G2.com.

What do you dislike about Confluence?

Search is my daily frustration. When I need to find a specific test plan or an older bug analysis doc, Confluence search often surfaces outdated drafts or duplicate pages first, so I've resorted to bookmarking key pages instead of trusting search which defeats the purpose of a knowledge base. The editor's table handling is my second complaint: my test case documents are table-heavy, and restructuring columns, copy-pasting rows from spreadsheets, or working with large tables is slow and error-prone compared to Excel or Sheets. Long documentation pages also become sluggish to edit, which I hit regularly with detailed test coverage docs. Finally, useful capabilities like AI-powered search and content summaries sit behind the Premium tier, so teams on Standard don't get help with exactly the problem (findability) the product most needs to solve. Better search relevance and native stale-page detection would fix most of this Review collected by and hosted on G2.com.

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

The core problem Confluence solves for me is scattered QA knowledge. Before, test plans, requirement analyses, and bug investigation notes lived across spreadsheets, chat messages, and local files — when a dev asked 'was this edge case covered?' or a PM asked 'why did we deprioritize that bug?', answering meant digging through history or relying on memory. Now every feature has a documented trail in one place: the PRD analysis, the test coverage doc, the gap analysis, and links to the related Jira tickets. The benefit shows up in three ways. First, repeat questions get a link instead of a re-explanation, which saves real time every sprint. Second, release retrospectives are faster because the reasoning behind test decisions is already written down next to the tickets. Third, when regression issues surface months later, I can trace exactly what was tested and what was flagged at the time — version history makes that audit trail trustworthy. It's turned QA documentation from something we did for compliance into something the whole team actually uses to make decisions. Review collected by and hosted on G2.com.