---
title: "Xray 3.5.0 Release Notes"
canonical: "https://docs.getxray.app/space/XRAY/301671173/Xray%203.5.0%20Release%20Notes"
format: markdown
---
> Macro (section)
> 
> > Macro (legacy-content)
> 
> > Macro (legacy-content)

> Macro (toc)

# Upgrading Xray to 3.5.x


<details>
<summary>Upgrading from versions < 3.2.x</summary>

**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 the upgrade. A  **re-index**  operation of your Jira instance is required so that the internal data becomes searchable and usable by Xray.

> ⚠️ Please be aware that this upgrade task will run <u><span style="color: #003366">immediately </span></u><span style="color: #003366">after</span> 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.
</details>

<details>
<summary>Upgrading from versions >= 3.2.x</summary>

**If you are upgrading from v3.2.x or v3.3.x to v3.5**, 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 to the Lucene indexes.

> ⚠️ As this operation can take some time and use a considerable amount of server resources, we suggest scheduling the upgrade of Xray and the recalculation of the custom fields, outside of business hours.
</details>

# Downgrading from Xray 3.5.x


<details>
<summary>Downgrading from any version</summary>

Downgrading from Xray 3.5.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.

### Historical Coverage Gadget

Some configuration parameters for this gadget were modified as a result of supporting multiple projects whenever using a saved filter as a source. It is possible that some users will get errors on the gadget after downgrading from 3.5.x. If this happens, please edit the configuration to ensure the gadget is configured properly.
</details>

#   
Release highlights 


> Macro (panel)
> 
> > Macro (legacy-content)



> Macro (panel)
> 
> > Macro (legacy-content)



> Macro (panel)
> 
> > Macro (legacy-content)

#   
  
And more...


| **Gadgets** | **Test Repository** | **Execution** |
| --- | --- | --- |
| - The Historical Daily Requirement Coverage Gadget now supports multiple projects when using a saved filter as source. The Gadget configuration parameters have also been simplified. | - You can now navigate directly from a Test issue into the Test Repository. The "Test Repository Path" custom field now contains a link that will open the Test Repository on the Test issue folder. | - A new project permission was added by Xray to override the permission to execute Tests. |


# New Features and Bug Fixes in this release

> Macro (jira)