Hi Alejandro,
Sorry to hear that your last upgrade was a difficult one. Data loss is not a typical problem Jira upgrades have. I have not seen very many upgrades that required you to make changes to the backup xml files in order to complete the data import. When I have seen this, it tends to be in regards to a plugin in Jira that was incorrectly storing data to one of the Active Objects table OR the new version of Jira is not able to load the plugin that understands that specific data. Is your Jira server by chance using an Oracle database on the back end?
On another related topic to your post: You mentioned wanting to upgrade to the latest version. However I am curious if you might be interested in getting onto an Enterprise release of Jira. More details in Atlassian Enterprise releases. We understand how difficult and painful it can be to upgrade Jira. So the enterprise release versions tend to be supported longer in regards to the number of fixes they get to their line. As of today, that would be 7.13.5. However I recommend checking that page to find the current enterprise release.
We also recommend Creating a test environment for Jira as a means to test out an upgrade of your data before you do so on a production environment. This is a good test run to understand what problems you might encounter. Moving Jira between major versions (such as between 7 -> 8), tends to require most plugins that Jira uses to need an upgrade to remain compatible.
Lastly, I'd also want to make sure that when you upgrade Jira, that the destination Jira site is using a supported platform. The database versions supported in Jira tend to change as time passes, and older databases might not be able to process the upgradetasks needed to maintain your data. Just something else to check in the process of upgrading Jira to avoid problems.
I hope this helps.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.