---
title: "Archiving Xray Issues"
canonical: "https://docs.getxray.app/space/XRAY/301403991/Archiving%20Xray%20Issues"
format: markdown
---
Jira Datacenter supports [archiving of issues](https://confluence.atlassian.com/adminjiraserver/archiving-an-issue-968669980.html) since v8.1. <span style="color: #172b4d">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 search results. </span>This enhances Jira performance because it stores less data in the indexes.

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 extends this feature by archiving some of its internal data.

The goal of this page is to describe the effects of archiving issues on Xray.

> Macro (toc)

# Archiving Test Executions

> ℹ️ Archiving old Test Executions is a good use case for archiving Xray issues, especially if continuous integration processes are used. These can quickly create many Test Execution issues while importing new execution results into Xray on a daily basis. These issues are good candidates to be archived.

Archiving Test Execution issues will hide them from:

- Test Executions section of the Test Plan issue view
- Xray built-in <span style="color: #172b4d">[reports](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301662463)</span> and <span style="color: #172b4d">[gadgets](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301405409)</span>
- <span style="color: #172b4d">[Document generator](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/160235683)</span> exports
- Search results from [Xray JQL functions](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301669523)

Archiving a Test Execution will also **archive its Test Runs.**

> ℹ️ Go [here](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301470346) to see more detailed information about archiving Test Executions and configuring the archiving process.


### Archiving Test Runs

Archiving a Test Execution issue automatically archives its related [Test Runs](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301502714). <span style="color: #172b4d">Doing so will </span>**not delete**<span style="color: #172b4d"> the Test Run information from database, instead they will be:</span>

- <span style="color: #172b4d">Read-only: You will still be able to navigate into the execution page and see the execution results but will not be able to edit</span>
- <span style="color: #172b4d">No longer used for the calculation of the Test Run Status and </span><span style="color: #172b4d">[Requirement Status](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301506247)</span>
- <span style="color: #172b4d">Omitted from the Test Runs section in the </span><span style="color: #172b4d">[Test](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301696435)</span><span style="color: #172b4d"> and </span><span style="color: #172b4d">[Test Execution](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/160137357)</span><span style="color: #172b4d"> issue view (including Overall Execution Status bar) </span>
- <span style="color: #172b4d">Hidden from the execution inner tables in the </span><span style="color: #172b4d">[Tests section of the Test Plan](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/160366867)</span>
- <span style="color: #172b4d">Excluded from Xray built-in </span><span style="color: #172b4d">[reports](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301662463)</span><span style="color: #172b4d"> and </span><span style="color: #172b4d">[gadgets](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301405409)</span>
- <span style="color: #172b4d">Hidden from </span><span style="color: #172b4d">[document generator](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/160235683)</span><span style="color: #172b4d"> exports</span>

<span style="color: #172b4d">A message will be shown in the Test and Test Execution issue view informing there are archived Test Runs:</span>

![image](media://80a4b5d6-4624-446a-9f9b-bb709e9e4660)

<span style="color: #172b4d">And also in the execution page:</span>

![image](media://a6932632-e141-4994-8629-6d725269fe92)

<span style="color: #172b4d">Test Runs archived via Test Execution issue can be restored at any time by restoring the Test Execution issue.</span>

# Archiving Tests

Archived Test issues:

- No longer participate in the calculation of Requirement Status
- Are no longer taken in account in the Test Coverage
- No longer appear in the Tests section in the Test Plan <span style="color: #172b4d">(including Overall Execution Status bar)</span>, Test Set and Pre-Condition issue view <sup>[1](https://getxraydocs.atlassian.net/wiki/display/XRAY630/Archiving+Xray+Issues#ArchivingXrayIssues-ImpactonXrayIssueLinks)</sup>
- Are hidden from Test Repositories and Test Plan Boards
- Are excluded from Xray built-in<span style="color: #172b4d"> reports, gadgets</span> and <span style="color: #172b4d">document generator</span> exports
- No longer appear in search results from Xray JQL functions

Archiving a Test will also **archive its Test Runs.**

### Archiving Test Runs

Archiving a Test issue will also archive its related Test Runs with the same effects described previously when archiving via Test Execution issue.

<span style="color: #172b4d">Test Runs archived via Test issue can be restored at any time by restoring the Test issue.</span>

# Archiving Test Plans

Archiving Test Plans will hide them from:

- Test Plans section in the Test issue view <sup>[1](https://getxraydocs.atlassian.net/wiki/display/XRAY630/Archiving+Xray+Issues#ArchivingXrayIssues-ImpactonXrayIssueLinks)</sup>
- Xray built-in <span style="color: #172b4d">reports</span>, <span style="color: #172b4d">gadgets</span> and <span style="color: #172b4d">document generator</span> exports
- Search results from Xray JQL functions

Archived Test Plans will also no longer be used as **scope for the Test Run Status and Requirement Status.**

### Effects in the Test Run and Requirement status scope

Archived Test Plans are no longed used as [scope](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301662486) for the Test and Requirements status custom fields, which affects the scope analysis of Requirements and Tests: After archiving a Test Plan *TP*, a given Requirement *R* that was <span style="color: #ff0000">**NOK**</span> in the scope of *TP* will be <span style="color: #3366ff">**UNCOVERED**</span> for the same scope *TP*.

Another effect of not being used as scope is that the Latest Statuses of Tests under a Test Plan issue will not be shown anymore. For this reason, when archiving a Test Plan, a message will be displayed informing of the situation:

![image](media://448fb56a-75eb-4bb1-afce-cdc70ad87494)

An archived Test Plan issue can be restored anytime, doing so will retrieve the Test Plan state prior to archiving and all of the Test Plan-scoped statuses for Tests and Requirements.

# Archiving Requirements

Archived Requirements will be excluded from:

- Xray built-in <span style="color: #172b4d">reports</span> and <span style="color: #172b4d">gadgets</span>
- <span style="color: #172b4d">Document generator</span> exports
- Search results of Xray JQL functions

Archiving Requirements will also **archive their Sub-Test Executions.**

### Archiving Sub-Test Executions

Each issue is archived along with all its subtasks.

In case a Requirement is archived, its [Sub-Test Executions](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/160367310) will be archived as well. A Sub-Test Execution has the same functionalities of a Test Execution so archiving them have the same effect as archiving a Test Execution issue, namely all its Test Runs will be archived.

# Archiving Test Sets and Pre-Conditions

Archived Test Sets and Pre-Conditions will be excluded from:

- Xray <span style="color: #172b4d">[reports](https://getxraydocs.atlassian.net/wiki/display/XRAY/Built-in+Reports)</span> and <span style="color: #172b4d">[gadgets](https://getxraydocs.atlassian.net/wiki/display/XRAY/Reporting+using+Gadgets)</span>
- <span style="color: #172b4d">[Document generator](https://getxraydocs.atlassian.net/wiki/display/XRAY/Document+Generator)</span> exports
- Search results of [Xray JQL functions](https://getxraydocs.atlassian.net/wiki/display/XRAY/Enhanced+querying+with+JQL)
- Test Sets and Pre-Condition sections in the Test issue view <sup>[1](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301403991)</sup>

# Archiving Projects

When archiving a Project all its issues are archived as well, including the Xray ones.

The effects of project archiving will be the same as archiving issues.

For example, the archived issues will no longer be present on JQL results and if Test or Test Executions are found, Xray will also archive their internal data, namely its Test Runs.

# Impact on Xray Issue Links

> ℹ️ This section refers to the Xray custom issue links only (e.g. Tests associated with Pre-Conditions, with Test Sets, etc.) and not to the Jira native issue links.

Whenever issues are archived, those will no longer be present on JQL search results.

Due to the fact that Xray Issue Data Table components, used for presentation of Xray issue associations, are built on top of JQL searches and that archived issues no longer appear in those search results, the links will no longer be shown in some issue views. Because of that, there is no way to know if an issue is still linked to an archived one.

Whenever this happens, a warning message will be displayed at the top of the affected Xray Issue Data Table informing that some associated issues are being hidden. The below image shows an example of the Test Sets section in a Test issue view after archiving one of its related Test Sets.

![image](media://c73d5a36-cf35-4662-bc0b-eba131162bc9)