On this page we highlight the following:
Visit the Version 3.x.x page for a full history of version 3 releases.
Please continue to report bugs and share your ideas for improvements and new features at support.refined.com!
Thank you!
Version 3.3 Release notes
22 March 2022
For information on upgrading & downgrading, see Upgrading to version 3.3
Version 3.3 Upgrading instructions
We always recommend to first upgrade on a separate test/staging instance.
Before upgrading, make sure that you have Jira version 8.6.0 or higher/Jira Service Management version 4.6.0 or higher.
Install version 3.3 via the UPM, or download and install it via the Atlassian marketplace.
There’s an automatic upgrade procedure that will run the first time you install from a 3.0-3.2 version to 3.3 or newer. This upgrade will update values in the Request Types module module to prepare it for the new features and functionality.
Downgrade
If you’d like to downgrade:
Uninstall Refined for Jira 3.3
Install Refined for Jira 3.2
The drawback here is that any changes made to My Requests module, Request Types module modules or the global My Requests overview pages while on the 3.3 version will not be transferred back to 3.2. Similarly, the automatic upgrade that prepares these modules only runs once, so any new changes made to the module once back on 3.2 will not migrate over once a new 3.3 upgrade is made. In that case, we recommend simply configuring up these modules again. You can export and store the old version of the layout and use that as the basis for updating.
Version 3.2 Release notes
15 June 2021
Version 3.1 Release notes
14 December 2020
Version 3.0 Release notes
11 February 2020
Version 3.0 Upgrade instructions
Refined for Jira 3.0 has two types of migrations: an automatic one that is triggered when the app is installed and a manual one that you have to start by entering the Refined Configuration page.
Please note that you need to perform the manual migration for the app to work as expected. You can do this directly after you have upgraded the app in UPM.
Upgrade instructions
Make sure that you are on Refined for Jira version 2.0.10 or later. If not, upgrade to version 2.0.10 or 2.1.10 before upgrading to 3.0.x. Go to Manage apps and find Refined in the list of installed apps. If you're not on the latest version, you should see a button to upgrade to the latest version. If you're not on the latest version and you don't see the Upgrade button, you can always download the jar file from the Atlassian Martketplace.
Click the Get started button. If you don't see the button, go to the Refined Administration. Click the button prompting to upgrade the data to finish the data migration.
If the manual upgrade does not finish
The manual upgrade task should not take more than half a minute to complete. If it doesn't finish within a minute, it is likely that the migration has failed. In this scenario, it's best to disable the Refined app until we have been able to find what has caused the migration to fail. Please raise a support ticket and attach your Jira support file to the ticket so we can immediately start investigating the cause.
What happens in the migrations?
In the automatically triggered background migration, data is moved from one table to another. In the user-triggered migration, data is added to the tables and some data is manipulated and placed back into the tables.
Can I downgrade?
The migrations change the database structure that is required for version 3.0. Once these migrations are done, you will need to roll back to an earlier version of your database in order to downgrade. Versions prior to 3.0 will not work as expected with the new data structure.