Since Xray uses issue types in order to map the different testing entities, you can utilize it to implement workflow mechanisms.

This is unique and powerful because it allows you to have full control of your testing process by controlling the transition of statuses in these issue types.

You can then also invoke post-functions when certain statuses are met, such as notifying certain stakeholders or generate detailed reports.

The following table summarizes the possible use cases for implementing Jira workflows on top of Xray issue types.

Issue TypeWorkflow usage scenarios
  • Manage specification lifecyle
  • Manage specification lifecyle
  • Disable tests for new executions
Test Set
  • Manage specification lifecyle
Test Execution
  • Manage execution lifecyle
Test Plan
  • Manage plan lifecyle

Using Jira workflows is not mandatory, but they can be used to enhance your process. General recommendations when using them:

  • Don’t overcomplicate the workflows, but respect your internal process.
    • Add "reviewing statuses” where appropriate (at specification and execution).
  • Define global workflows for your test-related issues as well as for your requirements.

Xray provides some workflow control mechanisms that are able to integrate with Jira workflows. All these settings can be found in Global Preferences.

It's possible to:

  • Disallow executions of Tests with workflow statuses
  • Disallow executions with workflow statuses
    • For Test Executions in specific status

Please note

The following workflows are just examples. Implement a workflow that best suits your needs.

Tests and Preconditions



  • Have a status for “deprecated” Tests; you can then disallow executions for Tests in this status, in the Xray settings.
  • Have an initial stage for the specification (e.g., “draft” or “new”) and then another status when it’s ready to be used.

Test Sets

In Test Sets, workflows can be used to identify if a given Test Set is fully specified or not. They can also be used (e.g., by companies/departments providing testing services) as a way to manage the implementation and the delivery of the Test cases associated with that Test Set.



  • You can eventually implement similar workflows for Tests, Preconditions and Test Sets.
  • In more conventional scenarios, it may be preferable to keep this workflow as simple as possible.

Test Executions



  • To keep it simple, you can have an initial status (e.g., “new”), another when it’s in progress (e.g., “in progress”) and then another when it’s finished (e.g., “closed”).
  • If your Test Executions need approval or you have a reviewing state, you can then disallow executions for it, in the Xray settings. 
  • You may need to have an interim status if you need to review the results of a Test Execution.It may be quite appropriate for both manual and automated testing (due to flaky tests).

Test Plan



  • Have an initial status (e.g., “new”), another when it’s in progress (e.g., “in progress”), and then another when it’s finished (e.g., “closed”).
  • You may need to have an interim status if you need to review the results of a Test Plan.
  • No labels