Sub Test Execution works exactly like a Test Execution, but, as it is a sub-task, it is created within the context of a requirement.
On the agile board, Sub Test Executions will be displayed as sub-tasks of the requirement.
Sub Test Execution must be added to your Issue Type Scheme.
Make sure that the agile board scope includes Sub Test Executions
Check the Agile Board Filter and confirm the issue type "Sub Test Execution" is included.
Review details at the step Setting scope for the Agile Board, from this module.
Make sure that the agile board scope includes Test Plan
Check the Agile Board Filter and confirm the issue type "Test Plan" is included.
Review details at the step Setting scope for the Agile Board, from this module.
Add the Test Execution Status
Go to the Project side Bar > Select Backlog or Active Sprint > Board > Configure.
Click the Card Layout and add the Test Execution Status to the Active Sprint.
Check the result
Get a quick view of all test executions of a requirement, directly from the Jira Agile board, as long as the executions are created as Sub-Test Execution issues.
Now your team can easily track all the work that needs to be done at the requirement level.
You may, for example, have different Sub Test Executions to test the requirement in different environments. By displaying the Sub Test Execution at your board, you can see the result for each environment.
Note that you are limited on the number of fields (3) you're able to include in each card on the board.