Versions Compared

Old Version 2

changes.mady.by.user Bruno Conde

Saved on

compared with

New Version 3

changes.mady.by.user Bruno Conde

Saved on

Key

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

...

Table of Contents

Upgrading Xray to 3.4.x

Upgrading from versions < 3.2.0

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 action is a one time action and it will run in the background, so that Xray is still available during upgrade. A re-index operation of your Jira instance is required so that the internal data becomes searchable and usable by Xray.

Upgrading from versions >= 3.2.x

If you are upgrading from v3.2.x to v3.4.y, you must recalculate data in Xray configuration section → Custom Fields. This recalculation is necessary because of a huge improvement in the amount of data that Xray need to add to the table and to Lucene indexes.

...

Downgrading from Xray 3.4.x to a version less than 3.2.0 implies that you must perform a re-index afterwards. This is because from Xray 3.2.0 onwards, the content and format of what Xray indexes has changed.


Release highlights 


Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section

Revamped Xray Issue Picker Dialog


Column
width60%

For restoring projects, Jira offers the built-in "Project Import" tool which allows partial, project imports (i.e. importing a specific project from a previous backup). 

This tool has some limitations though; it cannot transfer apps/add-ons related data between instances unless apps are prepared for it.

Fortunately, since v3.3, Xray is able of taking advantage of this mechanism; on previous versions, issues would be restored but the testing data wouldn't.

Thus, you can now use built-in backup&restore facilities of Jira:


  • for copying a project from one Jira instance to another Jira instance (e.g. from staging to production, or from internal to a DMZ instance)
  • to restore a project upon some mistake/data loss has been done in that project within an existing Jira instance


Learn more here.

Column
width40%






...