Summarize Blog
Quick Summary
Before you replace Xray, check which of your problems a new tool would fix, what you give up when tests stop being Jira issues, and what has to move with you. Includes a two-week plan for the switch.
Your Xray renewal is coming up, another project needs Xray’s test types set up, or the backlog search keeps returning Tests and Test Executions nobody asked for. Most lists of Xray alternatives give you ten tools and a price each. That doesn’t tell you whether a new tool fixes what’s slowing your team down, or what you give up when you move.
This guide is for QA leads and engineering managers whose team tests in Jira with Xray today. It helps you decide three things: whether a different tool fixes your problem, whether you still want tests to be Jira issues (Jira now calls these work items), and how to move without losing your test history.
We make AIO Tests, a test management app for Jira, and show how it handles a move from Xray near the end. Everything before that applies whichever tool you choose.
Which problems a new tool actually fixes
Xray does a lot well: tests as Jira work items you can search with JQL, a Test Repository with folders, reusable preconditions, BDD, custom fields on individual test steps, and AI test case generation in its Standard edition. Teams rarely leave because something basic is missing; they leave because of friction that shows up every week. Here’s how the usual reasons sort out:
If your reasons are mostly in the last two rows, a switch won’t help much. If they’re in the first five, it’s worth testing a replacement.
Do you still want tests to be Jira issues?
Once you know a replacement is worth testing, this is the first fork, and it’s the one most lists skip. Xray’s biggest strength and its biggest cost come from the same choice: every test, test set, test plan and test execution is a Jira work item. Leaving Xray usually means leaving that model.
Before you switch, list what you’ve built on your Xray tests: saved JQL filters, dashboard gadgets, workflows and automation rules. None of it carries over to a tool where tests aren’t work items. For many teams that list is short and the app’s own reports cover it; for others it’s the reason to stay.
The per-tester pricing that separate-tool vendors lead with is real: if six testers work on a 200-person Jira site, a per-tester tool can cost less. The trade is that everyone else leaves Jira to see test detail, and your team looks after two tools. Our guide to Jira test management tools compares the main Jira apps side by side.
What it costs
Price is the other half of that choice. Every Jira app on the Marketplace charges for each user on your Jira site, not only testers. Yearly prices for Jira Cloud, Standard edition, from the Atlassian Marketplace in November 2026:
TestRail, a separate tool, charges per tester: Professional is $38 a tester a month, billed annually.
What has to move with you
Price narrows the list, but a switch still fails when the history stays behind. Before you pick a tool, list what’s in Xray and ask each vendor what their migration brings across:
Watch two items: custom fields on individual steps, which not every tool has, and anything built on JQL over Xray tests.
A two-week plan for the switch
Trials on the Atlassian Marketplace run for 30 days, which is enough to test the move properly before you commit:
- Day 1: take stock. Count tests, test executions and projects, list your custom fields, saved filters, dashboards and automation frameworks, and note your renewal date.
- Days 2–3: import one project into the new tool, including its test plans, executions and results. Compare counts and open ten tests at random.
- Week 1: test both tools side by side. For one week (or one sprint, if yours are short), testers record results in both tools; Xray stays as the record.
- During that week: send one CI run through the new tool, fail a step on purpose and raise a bug, and build the report you’d send before a release.
- Week 2: decide. Ask a developer and a product owner what they could see on the story, and check your list of filters and dashboards has a replacement. If the new tool wins, move the remaining projects and update your CI jobs.
- Keep Xray until the reports match, and cut over before the renewal date.
Moving from Xray to AIO Tests
If your reasons for leaving were set-up, automation, reports or bugs, those are the areas where AIO Tests works differently from Xray. Our product team checked each row below in an Xray Standard trial in October 2026:
What carries over: folders, BDD and reuse. A published case can be added as a step in another, and Backgrounds (more than one per case) do the job of Xray’s Preconditions. AIO Tests also keeps earlier versions of a case.
What changes: tests aren’t Jira work items, so JQL filters and Jira dashboards built on them are replaced by AIO Tests’ reports.
What you lose: custom fields on individual test steps. If your team relies on them, check how you’d record that information before you move.
The migration utility brings across your tests, Test Repository folders, Test Sets, Preconditions (as Backgrounds), Test Plans and Test Executions with their run results, and our team helps you through the switch for free. Book a migration call.
Every row is in our full AIO Tests vs Xray comparison. If you’re also looking at Zephyr, see our guide to Zephyr alternatives for Jira. The migration guide covers mapping, validation and cut-over step by step.
Try AIO Tests on the Atlassian Marketplace
Frequently asked questions
What is the best alternative to Xray for Jira?
It depends on why you’re leaving. If tests in the backlog, set-up in every project, automated results or reports are the problem, look at apps that keep tests inside the app, such as AIO Tests. If your testers work outside Jira, a separate tool such as TestRail may fit.
Is there a free alternative to Xray for Jira?
AIO Tests and QMetry are free for Jira Cloud sites with up to 10 users. Xray costs $100 a year at that size.
Should test cases be Jira issues?
It’s a trade-off. As work items, tests work with JQL, workflows and dashboards, but they fill your backlog and need set-up in every project. Kept inside an app, tests stay out of the backlog and still link to stories and bugs, and you rely on the app’s own reports instead of JQL.
Can I migrate from Xray to another tool without losing history?
Usually, but check exactly what comes across: tests of each type, folders, test sets, preconditions, test plans, executions with results, and links to Jira work items. The AIO Tests migration utility moves tests, Test Repository folders, Test Sets, Preconditions (as Backgrounds), Test Plans and Test Executions with their run results.
Should I switch from Xray to Zephyr?
Zephyr keeps tests inside the app rather than as Jira work items, with folders, versioning, BDD and Call to Test for reusing one test in another. It’s worth a trial if you want that model. Our guide to Zephyr alternatives covers what teams look for when they leave it.
Is AI a good reason to leave Xray?
No. Xray’s Standard edition includes AI test case generation. Compare tools on set-up, automation, reports, bugs and your migration instead.
How we checked: Xray, Zephyr and AIO Tests features from our product team’s hands-on trials in October 2026, the same checks behind our comparison pages. Xray editions from its Atlassian Marketplace listing on 11 November 2026. Prices from the Atlassian Marketplace (Jira Cloud, Standard edition) and testrail.com in November 2026. Spot something out of date? Email help@aiotests.com and we’ll fix it.