...

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

...

...

• 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 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.

...

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 whenever when it’s ready to be used.

Test Sets

In Test Sets, workflows can be used to identify that 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, Pre-Conditions Preconditions and Test Sets.
• In more conventional scenarios, it may be preferable to keep this workflow as simple as possible.

...

• 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 needs 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. For Test Executions, it It may be quite appropriate for both manual and automated testing (due to flaky tests).

...