Filter the project records either by Project name you have given to the project or by the Project Key.
Derivation of Test Case Execution Status from Test Case Step Status
The derivation of Execution Status of test case and test step depends on the Derive Test Case Execution status from Test Case step status settings done in the Project module. The settings remain “On” by default, which derives test case execution status from test case step status and vice versa. But there can be scenarios wherein the derivation of execution status is not required. For example, if any of the test steps is getting failed or skipped due to some reason but the user still wants to mark the test case as “Passed”.
To address the need, an option to disable auto-deriving test case execution status from step statuses and vice-versa is provided under Project Settings.
→ Required Permissions: Project “Modify” rights are required to set this flag at the project level.
When the Derive Test Case Execution Status from Test Case Step Status settings are turned “On”: By default, the flag remains On. The test case execution status derives from test case step status and vice-a-versa as per the set priority of Execution Status as described in Execution Status Management .
When the Derive Test Case Execution Status from Test Case Step Status settings are turned “Off”: When the flag is turned Off, users need to change the test case status manually as it will not get changed as per the status assigned to test steps underneath.
For more details, refer to Test Executions Screen
Configure Resolved Status for Reports