Refined for Jira 3.0 is a major product update containing an amazing set of new features. We have also done significant changes in the underlying data structure to enable the new features and to improve performance. There are two types of migrations in this release, an automatic one that is triggered when the app is installed and a manual one that the user must start by entering the Refined Configuration page. Please note that you need to perform the manual migration in order for the app to work as expected. You can do this directly after you have upgraded the app in UPM.
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.
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.
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 is 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 at support.refined.com and attach your Jira support file to the ticket. This allows us to immediately start investigating the cause.