Admin feature only. |
As an Xray administrator, you can configure thresholds for archiving Test Executions.
Test Execution Archiving enables the cleanup of unused Test Runs and Test Executions, reducing the number of historical Test Runs that may add complexity without providing value or defining the status of any Requirements.
Check Test Run Archiving and Archiving Xray Issues for additional information. |
Archiving Test Executions allows you to hide them in Xray/Jira while preserving their data, so you can access it if needed later. This helps reduce clutter in Xray and Jira views, especially when importing automated Test results into Xray.
Test Runs can accumulate quickly, but usually, only the latest results are relevant. Older Test Execution Issues can be archived automatically by Xray, using Jira's Issue archiving mechanism.
Archiving Test Executions does not delete Test Run data. Archived Test Execution Issues are hidden from Issue views, Xray reports and gadgets, and will not appear in Issue searches. To locate them, you will need to save their Issue key.
You can access archived Test Executions like any other archived Issues in Jira; however, Test Run data will only be visible once the Test Execution Issue is unarchived.
All Test Executions within the selected projects (Figure 2 - 3) are eligible for archiving, except those with Test Runs that directly impact Requirement status. For example, if Requirement A is marked as "FAIL/NOT OK" due to Test Run A, this Test Run will not be archived, as it reflects the current status of Requirement A in Xray reports. The same holds true for Test Runs that affect the latest results in a specific version, Test Plan, or environment. Therefore, a Test Execution will only be archived if none of its Test Runs affect Requirement status and all Issues it contains are eligible for archiving.
|
|
If you have questions or technical issues, please contact the Support team via the Customer Portal (Jira service management) or send us a message using the in-app chat. |