Since Xray uses issue types in order to map the different testing entities, you're can take advantage of it in order 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 highly detailed reports; this can be quite useful.

The following table summarizes some possible aims for implementing JIRA workflows on top of Xray issue types.

Using JIRA workflows is not mandatory but they can be used to enhance your process. Some general recommendations on using workflows though:

• 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 and also for your requirements

Tests and Pre-Conditions

Recommendations

• Have a status for “deprecated” tests
• Have an initial stage for the specification (e.g. “draft” or “new”) and then another status whenever it’s ready to be used

Test Sets

Recommendations

• Ha

Test Executions

Recommendations

• Have an initial status (e.g. “new”) then 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 Execution; for Test Executions it may be quite appropriate, both for manual and automated testing (due to flaky tests)

Test Plan

Recommendations

• Have an initial status (e.g. “new”) then 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