Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderStylesolid
Section
Column
width33%

Upgrading Xray to 7.6.0


Expand
titleUpgrading from versions < 3.2.x

If you are upgrading from a version lower than 3.2, this This implies that an upgrade task will run to pre-calculate historical data. This one-time action will run in the background 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
titleUpgrading from versions 3.2.x and 3.3.x

If upgrading from v3.2.x or v3.3.x to v7, 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
width33%

Downgrading from Xray 7.6.0


Expand
titleDowngrading to any version

Downgrading from Xray 7.x.x to a previous version may 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


    And the precondition will show the warning of being linked to an archived test

...