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

Issue Type	Workflow usage scenarios
Pre-Condition	Manage specification lifecyle
Test	Manage specification lifecyle Disable tests for new executions
Test Set	Manage specification lifecyle
Test Execution	Manage execution lifecyle
Test Plan	Manage plan lifecyle

Don’t overcomplicate but respect your internal process
- Add "reviewing statuses” where appropriate (at specification and execution)
Define a global workflows for your test related issues and also for your requirements

Tests and Pre-Conditions

Xray for JIRA 3.0 > Using Jira workflows for testing purposes > image2017-10-11_11-6-14.png

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

Xray for JIRA 3.0 > Using Jira workflows for testing purposes > image2017-10-11_11-8-37.png

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/Plan; for Test Executions it may be appropriate, specially for manual testing

Xray for JIRA 3.0 > Using Jira workflows for testing purposes > image2017-10-11_11-8-37.png

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/Plan; for Test Executions it may be appropriate, specially for manual testing