How can we track and report test case re-executions in Zephyr?

Hello SmartBear Community,

We would like to know if there is a recommended way to customize or configure Zephyr so that we can clearly identify and track test case re-executions.

Currently, we have a testing scenario where the same test case may need to be executed more than once. This may happen because of a failed execution, a correction, a change in test data or parameters, or because the test needs to be validated again.

The main challenge is that, from a reporting and traceability perspective, it is difficult to determine how many times a specific test case has actually been executed.

For example, we would like to have visibility such as:

Test Case A: Executed 1 time
Test Case B: Executed 3 times
Test Case C: Executed 5 times
Test Case D: Executed 2 times

Ideally, we would like to capture this information through a custom field, execution-level field, counter, or another native Zephyr mechanism that allows us to identify the number of executions or re-executions associated with each test case.

Once this information is available, we would like to use it in reports or dashboards to analyze the number of executions and re-executions, for example:

Number of test cases executed only once
Number of test cases re-executed
Number of re-executions per test case
Test cases with the highest number of re-executions
Re-executions by application or system under test
Re-executions by test cycle
Re-executions by execution status or result

For example, if our test cases are associated with different applications, we would like to generate a report such as:

Application A

100 test cases executed
80 executed once
15 executed twice
5 executed three or more times

Application B

60 test cases executed
45 executed once
10 executed twice
5 executed three or more times

Our objective is to obtain better test execution traceability and metrics around rework and re-execution, rather than simply knowing the latest execution result.