upgrade path

Duro Oravsky September 24, 2012

Hi,

these are our current versions of your products

JIRA 3.13.5 #360 ent

we need to upgrade to the latest versions

JIRA 5.1.3 / 20 August 2012

here is the step-up plan for our upgrade

upgrade JIRA 3.13.5 -> 4.0

upgrade JIRA 4.0 -> 5.0

upgrade JIRA 5.0 -> 5.1.3

I am working and collecting all the upgrade documents related to these upgrades

could you please quickly comment whether all the inbetween-steps are required for the successful upgrade ?

eventually point out to documentation that deals with the these kinds od upgrades from very old versions

many thanks

-Duro Oravsky

Corel Corporation

1 answer

0 votes
MatthewC
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 26, 2012

Your first upgrade from 3.13.5 to 4.x is definetely needed to go above 5.0 but the recommended version is 4.4.x, I'd choose 4.4.5

https://confluence.atlassian.com/display/JIRA/JIRA+5.0+Upgrade+Notes#JIRA5.0UpgradeNotes-UpgradingtoJIRA5.0%28orlater%29fromaJIRAversionpriorto4.0.0

There is no real issue in upgrading from 3.13.5 to 4.4.5 but the notes are here, the big changes are 3.13.x to 4.0 and to 4.3

https://confluence.atlassian.com/display/JIRA044/JIRA+4.0+Upgrade+Guide

https://confluence.atlassian.com/display/JIRA044/JIRA+4.1.1+Upgrade+Guide#JIRA4.1.1UpgradeGuide-UpgradingfromJIRA4.0.xandEarlier

https://confluence.atlassian.com/display/JIRA044/JIRA+4.3+Upgrade+Guide#JIRA4.3UpgradeGuide-UpgradingfromJIRA4.2to4.3

so I'd do....

3.13.5 -> 4.4.5 -> 5.1.3

It's a lot of work to put back to back and I personally would do one upgrade, stop, run all the regression & user tests, get sign-off before going on to upgrade to 5.1.3. therwise you will get to the end and if you find a bug, you will have no idea where it all went wrong.

Also, backups... backup, backup, backup... database, disk, XML export.

It's the kind of job where, if you are not technically comfortable with, I'd contact an Atlassian partner

Suggest an answer

Log in or Sign up to answer