---
title: "Xray 3.4.0 Release Notes"
canonical: "https://docs.getxray.app/space/XRAY/301670788/Xray%203.4.0%20Release%20Notes"
format: markdown
---
**18 June 2019**
The Xray team is proud to announce the release of **Xray 3.4.0**.
The main goal for this version is to provide a set of features and improvements to support the basics of [Risk-Based Testing](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301473536). This testing strategy allows organizations to focus their testing and prioritize existing tests based on the assessed risk level, which depends on the likelihood and impact of failure.
As part of our continuous improvement, more performance improvements have also been included in this version.
Discover the key features below. 🙂
> Macro (toc)
# 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 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 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.
### Upgrading from versions >= 3.2.x
**If you are upgrading from v3.2.x or v3.3.x to v3.4.y**, 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 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 also the recalculation of the custom fields, outside of business hours.
# Downgrading from Xray 3.4.x
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.
### Overall Coverage Gadget
Some configuration parameters for this gadget where modified as a result of supporting multiple projects whenever using a saved filter as source. It is possible that some users will get errors on the gadget after downgrading from 3.4.x. If this happens, please edit the configuration to ensure the gadget is properly configured.
#
Release highlights
> Macro (panel)
>
> > Macro (legacy-content)
> Macro (panel)
>
> > Macro (legacy-content)
> Macro (panel)
>
> > Macro (legacy-content)
> Macro (panel)
>
> > Macro (legacy-content)
>
>
>
> > Macro (legacy-content)
> Macro (panel)
>
> > Macro (legacy-content)
> Macro (panel)
>
> > Macro (legacy-content)
#
And more...
| **Gadgets** | **REST API** | **Execution** |
| --- | --- | --- |
| - The Overall Requirement Coverage Gadget now supports multiple projects when using a saved filter as source. The Gadget configuration parameters have also been simplified. | - When importing Gherkin feature files using Xray REST API, the descriptions on the features will be also imported to the Requirement issue description. | - Only the Test Run assignee can execute the Test Run. This feature can be enabled/disabled on Xray configuration. |
# Just one more, yet important, thing...
> Macro (section)
>
> Documentation is always important and sometimes you may miss it. We added a set of relevant articles to our already extensive documentation.
>
> As this release provides a set of features that enable the basics of Risk-Based Testing, we've added a few related articles.
>
> On another topic, many teams are eager to adopt Agile and Agile Testing, we've specifically made some dedicated content for them, giving some background information on the earlier topics and providing concrete examples so you can get started or even become more agile.
>
> Finally, as teams grow they face additional challenges, including the demand for great performance. Performance is dependent on many different factors, starting with proper Jira setup, deployment type and also with Xray setup and usage patterns. Therefore, we created an article with a collection of setup, configuration and usage tips, to ensure you have the greatest performance on your deployment.
>
> Here's a sum up of all the relevant articles that we've added:
>
> - **[Performing Risk-Based Testing (RBT) with Xray](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301473536)**
> - [Risk-Based Testing](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301476977)
> - [Risk Management](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301673593)
> - [Agile software development](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301503941)
> - [Using Xray in an Agile context](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301677135)
> - [Leveraging Agility in Agile teams](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301409660)
> - [Agile values and principles with Xray](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301672416)
> - [Agile Testing](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301476069)
> - [Usage tips to improve performance](https://getxraydocs.atlassian.net/wiki/spaces/XRAY/pages/301504815)
# New Features and Bug Fixes in this release
> Macro (jira)
> Macro (__confluenceADFMigrationUnsupportedContentInternalExtension__)