...

Archived Test Plan will also no longer be used as scope for the calculation of Test Run Status and Requirement Status.

...

Archived Test Plans are no longed used as scope when analysing for the Test and Requirements statuses.status custom fields, which affects the scope analysis of Requirements and Tests: A given requirement R that was NOK in a given Test Plan TP will be UNCOVERED in the context of the Test Plan TP in case TP is archived.

Another effect of One of the effects 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:

...

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.

...

Archived requirements will be excluded from:

• Xray built-in reports and gadgets
• Document generator exports
• Search results of Xray JQL functions

Archiving requirements will also archive their Sub-Test Executions.

...

What happens when Test Sets and Pre-Conditions are archived?

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

• Xray reports and gadgets
• Document generator exports
• Search results of Xray JQL functions
• Test Sets and Pre-Condition sections in the Test issue view

What happens when Projects are archived?

When archiving a Project all its issues are archived as well. If any , this includes the Xray issues.

The effects on Jira and Xray will be the same as archiving issues.

Namely, if Test or Test Execution is Executions are 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.their Test Runs. 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: