Page History
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 Jira stores less data.
This page This Page describes the known impact and limitations of archiving issues in Xray.
| Info |
|---|
We have plans to support the Jira archiving feature and even extend this feature so that Xray issues can be archived without some of the undesirable side effects that are described on this page. A good use case for archiving Xray issues, will be to archive old Test Executions, especially if continuous integration processes keep importing new execution results into Xray on a daily basis. This feature is on our Roadmap. |
For more information on archiving issues please visit JIRA documentation.
...
Even though the Test is read only, it still can be executed from the Test Runs section and all the fields from the execution page can be edited (evidences, steps, comments, custom fields, etc).
...
The Test Execution will still contribute for the Test Run Status of the Test. This can create a lot of confusion to the user because the However the Test Execution will not be listed in the Test Run Section of the Test and there will be no indication that an archived Issue is affecting the Test Run Status.
...
The Test Issue still contributes to the Requirement Status, even after reseting this custom field. However the Test is not included in the Test Coverage and this may create confusion to the user because there and there is no indication that an archived Test is affecting the Requirement Status.
...
When archiving a Test it will still contributes to the Overall Execution Status. However this might cause confusion to the user because the , the Test will not be listed in the Tests Section.
...
- Test Run for archived Test is included in the Report.
- Test Run for archived Test Executions Execution is not included in the Report. This is not coherent with the archived Test behavior.
- Archived Defects are included in the report but JQL link will not work.
...
Even though the Test is read-only, the Test Run can still be edited using the endpoints (PUT|POST|DELETE) /rest/raven/1.0/api/testrun/{id}/status/*.
see Test Runs - REST.
Test Repository
When Using GET /rest/raven/1.0/api/testrepository/<projectKey>/folders the archived Test is included in counts.
PUT and POST can also be executed, even though the Test Issue is read-only.
Import Execution Results
...
- PUT on /testrun is possible even when Test is archived
- PUT on /testrun is not possible when Test Execution is archived
...
| JQL function | note |
|---|---|
requirements | The Requirement Status is still affected by the archived. It will return same results as if Test issue wasn't archived. |
requirementsWithStatusByTestPlan | The Requirement Status is still affected by the archived. It will return same results as if Test or Test Plan issue wasn't archived. |
testTestSet | Returns associated issues, even if issue passed as argument is archived. |
testTestSet | Returns associated issues, even if issue passed as argument is archived. |
testsWithNoTestSet | Returns associated issues, even if issue passed as argument is archived. |
testPreConditions | Returns associated issues, even if issue passed as argument is archived. |
preConditionTests | Returns associated issues, even if issue passed as argument is archived. |
testRequirements | Returns associated issues, even if issue passed as argument is archived. |
requirementTests | Returns associated issues, even if issue passed as argument is archived. |
testExecutionTests | Returns associated issues, even if issue passed as argument is archived. |
testTestExecutions | Returns associated issues, even if issue passed as argument is archived. |
testSetPartiallyIn | Returns associated issues, even if issue passed as argument is archived. |
testSetFullyIn | Returns associated issues, even if issue passed as argument is archived. |
testPlanTests | Returns associated issues, even if issue passed as argument is archived. |
testPlanTestExecutions | Returns associated issues, even if issue passed as argument is archived. |
testPlanRequirements | Returns associated issues, even if issue passed as argument is archived. |
testTestPlan | Returns associated issues, even if issue passed as argument is archived. |
Xray Integrity Checker
There is a peculiarity with the following entries of the Xray Integrity Checker
- Clear Test Set Test Count and Test Plan Test Count Custom Field
- Clear Test Execution Defects Custom Field
Let's take the example of an archived Test Set with associated Tests. Running the clear Test Count will clear the value for the issue and, after opening the archived Test Set issue, the value will not be recalculated because the issue is read-only.