Jira Datacenter supports archiving of issues and projects since v8.1. By archiving issues, Jira will remove them from the indexes. The archived issues will still be accessible in read-only mode, however, they will not appear in Jira searches. This enhances Jira performance because it stores less data in the indexes.

As many of the Xray entities are normal Jira issues, it already supports this feature . Archiving at some extent. So, archiving its issue types has the same effect of archiving any other Jira issue type, - namely archived issues no longer appear on JQL search results and on reports. Additionally, Xray extends this feature by archiving or removing some of its related data.

The goal of this page is to describe the behaviour of Xray whenever its issues are archived.

Archiving Test Executions

...

Archiving a Test issue automatically archives its related Test Runs with the same effects described on the previous section. Additionally, archived Tests are no longer used for the calculation of the Requirement Status and are hidden from the Requirement Test Coverage analysis, Test Plan Overall Execution Status bar and any other kind of analysis involving these Tests.

Archiving Test Plans

...

Effects of Issue Archiving on Xray built-in reports and gadgets

Archived issues and test runs no longer appear on reports, gadgets and on documents exported by docgen ...

Effects of Issue Archiving on the 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.