All my configuration has gone after upgrading from 1.0.x

Owned by Andy Brook [Plugin People] (Unlicensed)
May 10, 2012

Answer

Don't panic, no configuration is lost.

The plugin key was broken in 1.0.x, meaning the UPM would never report updates. The plugin key was fixed in 1.1, but as a result, JIRA treats it as an entirely new plugin, hence two sets of data. A specific one-time upgrade step is required.

Hopefully you have not installed the 1.0 version and the 1.1 version side by side, they will co-exist but it wont work as there 'can be only one' UI. Uninstall 1.1 to get an active 1.0 plugin again.

In order to minimise pain, a full Profile export was implemented, upgrading to 1.0.6.1 first, will gain this feature. The exported XML data can then be reimported later. Please see the 1.1 Release Notes for details.

Historic data loss

Unfortunately, in this scenario its not a trivial task to transfer audit history to the new tables. I hope this problem has been caught early enough to not inconvenience users too much. All old audit data and testcases should be removed at the time of the plugin update to 1.1

After upgrade, there will be two sets of JEMH tables reported in the Plugin Storage section of the Administration screens (can be seen in the database), these are:

  • AO_806D40_.... (old 1.0.x)

  • AO_78C957_... (new 1.1.x)

Once the data migration has completed, the older AO_806D40_.... tables can all be removed during a maintenance window.