We are just evaluating the migration from Jira 3.13. to 5.1
It works fine now by installing a new 4.x version, migrating old db and then upgrade to 5.1
Is there a way to update the new testing version with the contents of the productive 3.13 system, without going through the two update steps and loosing all the plugins and settings we made to the new system ?
Thanks in advance
The recommended method is to upgrade on two phase actually, first to 4.3 and above (4.3.x-4.4.x) then to 5.1. This is to ensure that the major migration process done in one upgrade phase so that the troubleshooting process will be easier if something happen.
For your information, JIRA 4.3.x-4.4.x is where the user migration occurred, then you could go straight to 5.x. However as describe earlier, it is recommended to upgrade to 4.3.x.
In order to upgrade with your plugin intact, you could try the following steps on your staging environment and see how it goes:
Hope it helps.
I've never done this two-phase recommendation that Atlassian recommends (either for jira or confluence). I believe they recommend it just so that it's easier for them to diagnose problems if there are any. The key thing is to test the migration on a copy of your production dataset. If it works you can do it in one fell swoop in production.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs