The recommended method is to upgrade on two phase actually, first to 4.4 (or 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.4.x.
Before performing any upgrade on production please test the upgrade on a test instance.
Rahul
It should work directly from 4.2 to 5.2. And which ever method you try, please try on a test system before attempting the production system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My recommendation would be 4.2 -> 4.4 -> 5.2
For more detailed information on the upgrading process, you can refer to this documentation : https://confluence.atlassian.com/display/JIRA/Upgrading+JIRA
if you plant to migrate JIRA to another server on the process of upgrading, you can refer to this documentation as well:
https://confluence.atlassian.com/display/JIRA/Migrating+JIRA+to+Another+Server
Please do take not that If you are migrating your JIRA, you might want to take note that your JIRA attachment files are not in your database, or in any XML backups, rather you would have to transfer the file from your old JIRA Home to your new JIRA Home.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.