A Practical Guide to Managing Xray Tests in Jira: 7 Steps
Struggling to track Xray tests in Jira? Follow 7 practical steps for xray test management for jira and spot coverage gaps before release. Read now.
If Xray tests in Jira are scattered across issues, releases, and teams, it becomes hard to see what is covered and what still needs attention. Missed links can hide requirements without tests, while unclear execution results make release decisions feel like guesswork.
You can manage Xray tests more reliably by setting a clear testing scope, creating reusable tests, organizing them into plans and executions, and linking them to requirements. Then review results and coverage regularly. Here’s why: a consistent workflow makes gaps easier to spot before release. I’ll walk you through seven practical steps, common problems to watch for, and ways to improve coordination around testing.
How to manage Xray tests in Jira: 7 steps
Start by defining what you need to test and how you’ll measure completion. Then build a repeatable path from requirements to test results, using Xray’s test issues and Jira links to keep the work connected.
-

Step 1: Define the testing scope
Choose the product area, Jira project, release, or sprint you’re testing. Write down the features in scope, the environments you’ll use, and the risks that deserve extra attention.
For example, a checkout release might include payment, discount codes, and order confirmation. Clarifying those boundaries helps you avoid testing unrelated features while overlooking critical ones.
-
Step 2: Agree on test types and statuses
Confirm how your team will use Xray issue types such as Test, Test Set, Test Plan, Test Execution, and Precondition. Agree on statuses and ownership so teammates interpret progress consistently.
A simple convention might distinguish tests that are ready, in progress, passed, failed, or blocked. The exact status options depend on your Jira and Xray configuration.
-
Step 3: Create clear, reusable tests
Write each test with a specific purpose, required preconditions, clear steps, and an expected result. Include enough detail for another tester to repeat it without asking what you meant.
For example, “Apply a valid discount code at checkout” is more useful when the test states the required cart contents and the expected total. Reuse a test when the same behavior needs checking in different releases.
-
Step 4: Organize tests into sets and plans
Use Test Sets to group related tests, such as payment checks or account access checks. Use a Test Plan to define the testing scope for a release or milestone, then include the relevant tests.
This separation makes it easier to reuse a group of tests without confusing a reusable collection with a specific release plan. Keep names meaningful, such as “Release 4.2 — Checkout Regression.”
-
Step 5: Link tests to requirements
Connect each test to the Jira requirement, story, or other work item it verifies. Review the links for missing coverage and tests that no longer match a requirement’s behavior.
For instance, if a story says customers can reset a password, its linked tests could cover a valid reset, an expired link, and an unknown email address. The links help reveal which acceptance criteria still lack checks.
-
Step 6: Run test executions and record outcomes
Create a Test Execution for the run you’re performing, then record each result against the relevant test. Add useful notes when a test fails or is blocked, including the environment and the observed behavior.
For example, a failed payment test may pass in one environment and fail in another. Recording the environment alongside the outcome gives the team a clearer starting point for investigation.
-
Step 7: Review coverage, failures, and next actions
Before a release decision, check that in-scope requirements have relevant tests and that execution results are current. Review failed and blocked tests with the people responsible for resolving them.
If your team runs automated tests, connect their results through an integration supported by your Xray deployment. Use recurring failure patterns to improve test steps, environments, or the underlying product.
How Xray’s test issues fit together
Xray uses different issue types to support different parts of a testing workflow. A Test describes a check, a Test Set groups related tests, and a Test Plan collects work for a defined scope, such as a release.
A Test Execution records results from a particular run. A Precondition captures conditions that must be true before a test can run. For example, a payment test might require an active account and a configured test payment method.
Let me explain: these issue types are most useful when each has a clear role. If a team treats a Test Set and a Test Plan as interchangeable, testers may duplicate groups or struggle to tell which tests belong to a release.

Build traceability from requirements to results
Traceability means you can follow the relationship between a requirement, the tests that check it, and the results of those tests. Jira issue links help create that path, but only when the team adds and maintains them consistently.
Imagine a story requiring a user to update an account email address. You might link tests for a valid new address, an already-used address, and an invalid format. When one test fails, the team can see which requirement needs attention.
Review links when requirements change. A test that was accurate last month may no longer cover a revised acceptance criterion, even if its title still sounds relevant.
Keep the testing workflow manageable
Agree on a few team conventions before test volume grows. Define how to name tests, when to create a new Test Plan, who updates results, and what evidence belongs in a failure note.
For example, a team might start test names with the feature area and action, such as “Profile — Change email.” It can then group related checks in a Test Set and create a separate Test Execution for each environment.
The best part? You don’t need a complicated process to get useful consistency. Start with a small set of rules, then adjust them when real testing work exposes a gap.
Use results to improve release decisions
Test results can help a team understand risk, but a pass rate alone rarely tells the whole story. A release with many passed tests may still have an untested high-impact requirement or a critical failure hidden among lower-priority issues.
Review coverage, outstanding failures, blocked tests, and the importance of affected features together. A failed test for a minor visual detail may carry a different release risk from a failed payment flow.
When automated results are part of the process, check that they map to the right tests and executions. If a result appears under the wrong test, correct the mapping before using it to guide a release decision.
Project coordination solution: ONES.com

Value proposition
ONES.com brings project management and knowledge management together through ONES Project and ONES Wiki, which are sold separately. If your challenge extends beyond running Xray tests to coordinating requirements, delivery work, and team guidance, ONES Project offers Jira-compatible workflows and built-in reporting.
ONES Project is a Jira alternative, not an Xray test-management replacement. Consider it when you’re evaluating broader project coordination needs alongside a testing workflow.
Core capabilities
- Pain: Teams need work items to follow their delivery process. ONES capability: Custom workflows can reflect team-specific stages. Result: Work moves through a process that better matches how the team operates.
- Pain: Standard fields don’t capture the details a team needs. ONES capability: Custom fields let teams record relevant work-item information. Result: Teams can organize and review work with more useful context.
- Pain: Sprint planning and tracking feel disconnected. ONES capability: Sprint management supports planning and tracking sprint work. Result: Teams can keep delivery activity visible within their project workflow.
- Pain: Progress is hard to assess across active work. ONES capability: Built-in reporting provides project reporting capabilities. Result: Teams can review progress without relying on a separate reporting plugin for common needs.
- Pain: Repetitive project actions take time. ONES capability: Automation supports recurring workflow actions. Result: Teams can reduce manual steps in suitable processes.
- Pain: Teams want a Jira-compatible way to manage project work. ONES capability: Jira-compatible workflows support familiar project patterns. Result: Teams can evaluate an alternative without assuming every process must be redesigned.
- Pain: Some organizations need to host project management within their own environment. ONES capability: Deployment options include Cloud, On-Premise, Private Cloud, and Air-gapped. Result: Teams can assess an arrangement that fits their environment.
- Pain: Self-hosting can raise concerns about missing features. ONES capability: ONES.com provides full feature parity between cloud and self-hosted versions. Result: Teams can consider self-hosting without a stated feature gap between those versions.
Application scenarios
- Coordinating a release: A product team can use ONES Project to manage requirements, sprint work, custom fields, and reporting while keeping its Xray testing process distinct.
- Working in a restricted environment: An organization can evaluate On-Premise, Private Cloud, or Air-gapped deployment options for project management, with deployment choice guided by its operational needs.
- Connecting project work with team guidance: A team can consider ONES Project for delivery coordination and ONES Wiki for knowledge management. The products are sold separately.
ONES.com offers a free plan for up to 30 seats. Evaluate its project-management capabilities against your team’s needs, and keep Xray-specific test planning and execution requirements in view during any comparison.
- Tests are hard to understand: Vague titles or missing expected results can make execution inconsistent. Give each test a clear purpose, repeatable steps, and an observable expected outcome.
- Requirements have missing test links: A story may appear complete while important behavior remains unchecked. Review in-scope requirements for relevant tests before each release or milestone.
- Results lack enough context: A failure without environment details can be difficult to reproduce. Include the environment and observed behavior when recording an issue.
- Test groups become confusing: Teams may duplicate work when Test Sets and Test Plans have unclear purposes. Agree on what each issue type represents and use consistent names.
FAQs about managing Xray tests in Jira
What is the difference between a Test Set and a Test Plan in Xray?
A Test Set is a group of related tests that can be reused, such as checks for account access. A Test Plan organizes testing for a defined scope, such as a release or milestone. A plan can include tests drawn from relevant sets. Teams should agree on these roles so they can reuse test groups without treating each release plan as the same thing.
How do I make sure Jira requirements have test coverage?
Link relevant Xray tests to the Jira requirements, stories, or work items they verify. Review those links against the acceptance criteria, especially after a requirement changes. For a password reset story, for example, coverage might include a valid reset, an expired link, and an unknown email address. A link is useful only when the test still checks the current requirement.
How should I handle a failed Xray test?
Record the outcome against the relevant Test Execution and add enough context for someone else to investigate. Include the environment, observed behavior, and any useful reproduction details. Then check whether the failure points to a product issue, a test-step problem, or an environment problem. Keep the result visible until the team has agreed on the next action.
Can Xray manage automated test results?
Xray can be used with automated testing workflows through integrations supported by your particular deployment. Confirm the available integration and result format for your Xray setup before designing the process. Make sure automated results map to the correct tests and executions, then review failures with enough context to investigate them. A result that is mapped incorrectly can give the team a misleading view of coverage.
Conclusion
Reliable Xray test management in Jira starts with a defined scope, clear test steps, and useful organization. Link tests to requirements, record execution outcomes with context, and review coverage before making release decisions.
When testing gets scattered, release risk becomes harder to see. A seven-step workflow gives your team a practical way to find gaps and act on failures. Start with the next release, agree on a few conventions, and improve the process as your team learns what works.