Page History
...
As many of the Xray entities are normal Jira issue objects, archiving its issues has the same effect of archiving any other Jira issue type. But additionally, Xray additionally extends this feature by archiving some of its internal data.
The goal of this page is to describe how Xray handles the archiving feature and the effects of it.
| Table of Contents |
|---|
Archiving Test Executions
...
Archiving a Test Execution issue automatically archives its related Test Runs as well. Archiving Test Runs will not delete the Test Run information from database, they are just hidden from issue views, reports, gadgets, are read-only and will no longer be instead they will be:
- Read-only
- Still be possible to navigate into the execution page and see the execution results
- No longer used for the calculation of the Test Run Status and Requirement Status
...
- Hidden from reports, gadgets and document generator exports
Test Runs archived via Test Execution issue can be restored at any time by restoring the Test Execution issue.
...
Archived Test Plans are no longer used as scope for the Test Run Status and Requirement Status,
Xray built-in reports and gadgets
Archived issues and test runs no longer appear on reports, gadgets ...
Xray Document Generator exports
Archived issues and test runs no longer appear on documents exported by docgen ...
Issue data tables sections
Whenever an issue is archived it is removed from the Lucene indexes and thus no longer appears on JQL search results. This has impact on some of the Xray issue data tables used to present the associations between issues.
Archiving Requirement issues
Archiving Pre-Conditions and Test Sets
Archiving Projects
When archiving a Project its issues are archived as well. If any Test or Test Execution is found, Xray will archive its internal data, namely the Test Runs will be archived and the Tests will be hidden from the Test Repository and Test Plan Boards.
This can be a long running task depending on the amount of Xray internal data to handle. Currently, Jira provides no way of knowing the progress of a project archival. However you can use this:
Effects on Xray built-in reports and gadgets
Archived issues and test runs no longer appear on reports, gadgets ...
Effects on Xray Document Generator
Archived issues and test runs no longer appear on documents exported by docgen ...
Effects on Issue data tables sections
Whenever an issue is archived it is removed from the Lucene indexes and thus no longer appears on JQL search results. This has impact on some of the Xray issue data tables used to present the associations between issues.