If you are upgrading from a version lower than 3.2, this implies that an upgrade task will run to pre-calculate historical data. This one-time action will run in the background so that Xray remains available during the upgrade. A re-index operation of your Jira instance is required to make the internal data searchable and usable by Xray.
Note
Please be aware that this upgrade task will run immediately after updating Xray. As this operation can take some time and use a considerable amount of server resources, we suggest scheduling the upgrade of Xray outside of business hours. It is always possible to cancel the recalculation operation in the Xray configuration section → Custom Fields → Maintenance.
Expand
title
Upgrading from versions 3.2.x and 3.3.x
If upgrading from v3.2.x or v3.3.x to v6v7, you must recalculate data in the Xray configuration section → Custom Fields. This recalculation is necessary because of the huge improvement in the amount of data that Xray needs to add to the table and the Lucene indexes.
Note
As this operation can take some time and use a considerable amount of server resources, we suggest scheduling the upgrade of Xray and recalculating the custom fields outside of business hours.
Column
width
33%
Downgrading from Xray
6
7
Expand
title
Downgrading to any version
Downgrading from Xray 57.x.x to a previous version will have the following side effectson Test Runs with a dataset:
Test parameters will no longer be converted on the Test Run page; this includes Test Step definitions and Pre-Conditions;
When loading a Test Run created on version 5.x.x, the merge/reset message will be displayed;
When merging a Test Run created on version 5.x.x with the new Test Step definition, all Test Step results will be updated but the reset/merge message will still be displayed;
A Test Run created on version 5.x.x with iterations will be displayed in a "flat mode." The iterations will no longer be available and all the Test Step results from each iteration will be presented in the Test Steps section; Image Removed
After the downgrade, the integrity checker will fail on "Check for invalid Mementos" for all Test Runs created on version 5.x.x. We recommend running the integrity checker before downgrading to eliminate possible invalid mementos.
Downgrading from Xray 6.x.x to a previous version will have the following side effects:
After creating some specific data using Test Case Versions, the user may have some glitches when downgrading to a specific version of Xray
On a Test Issue, multiple manual test versions with steps, when downgrading the test issue will show all steps from all the versions
On a Test Issue, multiple manual test versions with specific datasets, when downgrading the test issue will show the parameters from all the datasets
On a Test issue, having different test versions linked to the same precondition issue when downgrading, the test issue will show an integrity error instead of showing the precondition table
Image Added And the precondition will show the warning of being linked to an archived test Image Added
Test Issue:
A Call Test will be converted to a regular test step with a warning message Image Removed
Test Run PageThe Merge/Reset action will be displayed
Expand
title
Downgrading to versions ≤ 4.1.x
The Test Step Custom Fields and Test Run Custom Fields of the type "User Picker" must be deleted in the project configuration as they are not supported. Following that, the Test Runs that are using a User Picker field will have to be merged or reset. This includes Test Runs with the field for the Test Run itself and Test Runs for Manual Tests where the Test Steps contained the User Picker field.
Expand
title
Downgrading from any version
Downgrading from Xray 6.x to a version less than 3.2.0 implies performing a re-index afterward. This is because from Xray 3.2.0 onwards, the content and format of what Xray indexes have changed.
Historical Coverage Gadget
Some configuration parameters for this gadget were modified due to supporting multiple projects using a saved filter as a source. It is possible that some users will get errors on the gadget after downgrading from 4.x. If this happens, please edit the configuration to ensure the gadget is configured properly.
