The obligatory disclaimer
We built TrueStory, so obviously we have a bias. I'm going to try to be fair here, and I'll point out where the other tools do things better than ours. If you catch me being unfair, email us at hello@true-story.tech and I'll fix it. That said, take this with a grain of salt, go try all three, and decide for yourself.
Why these three
If you search "Jira test management" you'll find dozens of tools. But in practice, most teams end up looking at Zephyr Scale and Xray. They're the established players with the biggest install bases. TrueStory is the new kid. We built it because we used both of the others and felt like something was missing.
What was missing, specifically, was PR gating. But I'll get to that.
The quick comparison
| Feature | TrueStory | Zephyr Scale | Xray |
|---|---|---|---|
| Core idea | QA orchestration tied to PRs | Full test management platform | Tests as Jira issues |
| Built on | Forge (Atlassian-hosted) | Forge/Connect | Connect |
| AI test generation | BYOK (your own Claude/GPT/etc. key) | Limited | Built-in |
| QA gate for PRs | Yes (GitHub, GitLab, Bitbucket) | No | No |
| Confluence reports | Auto-generated | Available | Available |
| Automated testing | Not the focus | Yes | Yes |
| Free tier | Yes | No | No |
What Zephyr does well
Zephyr Scale has been around for a long time and it shows, in a good way. The feature set is deep. Test cycles, folder organization, custom fields, parameterized testing, built-in reports with pretty dashboards. If your QA team is 10+ people and you need a proper test management system, Zephyr delivers that.
Their reporting is really good. Traceability matrices, execution trends, defect density, the kind of stuff a QA lead shows in a sprint retrospective. We don't have that level of reporting yet, and I won't pretend we do.
They also handle automated test results well. If you run Selenium or Cypress and want to import results back into Jira, Zephyr has a clear workflow for that.
Where Zephyr frustrated us: It felt heavyweight for what we needed. We're a team of 8. We didn't need test cycles and folders and parameterized execution. We needed "here are the tests for this PR, go test them." Also, there's no way to block a PR merge based on QA results without building your own glue code, and the per-user pricing added up fast.
What Xray does well
Xray's big idea is that tests should be Jira issues. A test case is a Jira issue with type "Test." A test execution is a Jira issue. A test plan is a Jira issue. Everything lives in the same place where your stories and bugs live.
This is actually clever if you think about it. You get Jira's full workflow engine for your tests. You can move them through statuses, assign them, link them, put them in sprints. Your QA engineer works entirely in Jira's native interface.
Xray also has strong BDD/Gherkin support. If your team writes feature files and you want those connected to Jira, Xray handles that natively. Their automation integration with Cucumber, Robot Framework, etc. is solid.
Where Xray frustrated us: The "everything is an issue" approach cluttered our backlog. We had sprints with 15 real tickets and 40 test issues mixed in. Yes, you can filter them out, but it added friction. Also, same as Zephyr, no PR gating. And the setup was more involved than we expected. We spent the better part of an afternoon just configuring issue types and workflows.
What TrueStory does differently
I should be upfront about what TrueStory is and isn't. It's not a full test management platform. It doesn't do automated test results, BDD scenarios, test environments, or parameterized testing.
What it does is this: you link test cases to Jira tickets, someone opens a PR, and TrueStory makes sure those test cases get executed before the PR can merge. That's the core loop. Everything else (AI generation, Confluence reports, coverage analytics, email notifications) supports that core loop.
The QA gate is the thing neither Zephyr nor Xray offers. When a developer opens a PR on GitHub, GitLab, or Bitbucket, TrueStory automatically creates a testing session and sets a pending check on the PR. QA completes testing in Jira. The check goes green or red. The developer doesn't need to ping anyone, and the tester doesn't need to go to GitHub.
We also went with a bring-your-own-key model for AI. You plug in your own API key for Claude, GPT-4, DeepSeek, or Gemini, and generate test cases from ticket descriptions. Your data stays within Atlassian's infrastructure. It goes straight from Forge to the AI provider without touching our servers. That mattered to us, and it matters to teams with strict data policies.
Where TrueStory falls short: No automated test integration. If you run a Selenium suite and want those results in Jira, use Zephyr or Xray. Our reporting is simpler. We do Confluence reports per session, but we don't have traceability matrices or trend dashboards yet. And we're newer, so the ecosystem (community posts, tutorials, Stack Overflow answers) is thinner.
The pricing elephant
Let's talk money. Zephyr and Xray both use per-user pricing. Depending on your tier, you're looking at roughly $10-30 per user per month. For a team of 20, that's $200-600/month. For 50 users, it's real budget.
TrueStory has a free tier. For small teams, you can use the full feature set without paying. Check the Marketplace listing for current details. I won't put specific numbers here because they might change.
I'm not saying price should be the deciding factor. A tool that does exactly what you need at $30/user/month is better than a free tool that doesn't. But if you're a small team or a startup watching your Atlassian bill, it matters.
So which one should you pick?
Here's my honest take:
Pick Zephyr if you have a dedicated QA team that needs structure: folders, cycles, parameterized tests, detailed reporting dashboards. If your QA lead currently tracks everything in spreadsheets and wants to move to a proper system, Zephyr is the mature choice.
Pick Xray if your team thinks in BDD terms, writes Gherkin scenarios, and wants tests deeply woven into the Jira issue model. If you're a "everything should be a Jira issue" kind of team, Xray respects that philosophy.
Pick TrueStory if what you really want is to stop merging untested PRs. If your pain point is "we have tests but nobody enforces testing before merge," and you want AI to help draft the tests faster. If you want something lighter that doesn't take a day to configure.
Or try all three. They all offer trials. The best test management tool is the one your team actually uses.
Written by the TrueStory team. We tried to be fair. If we got something wrong about Zephyr or Xray, tell us and we'll correct it. hello@true-story.tech.