Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,521
Community Members
 
Community Events
168
Community Groups

Hello, we're currently using jira 5.0.7 and have a proposed plan to upgrade to 8.13.0.

could any one please help me with the best and successful version path...?

 

1 answer

1 accepted

0 votes
Answer accepted

You must upgrade through several versions if you do not want to break your data completely.

I would take 5.0 -> 5.2 -> 6.0 -> 6.4 -> 7.0 -> 7.13 -> 8.13 (if that's still the target by the time you've gone through all of tests)

Some of these may be skipped for mid-range or higher versions, but if you're going to do that, please make sure you test test test.

For example, you may be able to go from 5.2 to 6.3 to 7.0, or possibly even 5.0 to 6.3 to 7.0.  But you are likely to be in a world of pain if you try to go from 6.2 or lower to 7.0

You must not skip 6.3 or 6.4 to 7.0.  If you do, you will find certain stuff stops working in 7.8ish and above.  I would also not try to go from anything lower than 7.9 to 8.anything.

Thank you so much for quick response!!

 

We're currently thing to update all ALM tools, as part of that could you please help us with below applications aswell. i've mentioned current versions and proposed versions, could you please help us with the upgrade paths for each applications if possible, thanks.

 

Application   Current version           proposed version

Confluence      4.3.2                               7.8

Bamboo           4.2.1                               7.1.2

Crucible            2.9.2

Application     Current version   proposed version

Crucible           2.9.2                    4.8

FishEye            2.9.2                     4.8

 

we are considering to go with JIRA 8.8 instead of 8.13.0, would it still be same update path or can we skip any. please advice. thank you!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events