I am planning to upgrade from JIRA 5.1.5 to 6.1.7.

Do I need to step through the intermediate releases? Also would like to know if the overall upgrade to 6.1.7 affects the database schema, and that if so, that those changes are included in the overall process.


1 answer

1 accepted

1 vote
Accepted answer

I'd strongly recommend reading the release notes for each version (5.2, 6.0, but you can skim the point releases as they're generally minor tweaks and bug fixes), and testing the process several times, but yes, your upgrade plan can be as simple as:

  • Tell users to get out
  • Backup
  • Install new version (I usually pre-install it separately from the old one)
  • Copy stuff from home directory on old system to new one
  • Point new version at old database (ideally, a copy, so you can revert quickly if it goes bang)
  • Start new version
  • Wait as it'll do the entire upgrade for you
  • Test
  • Tell users it's ready

But seriously, test the process. A lot.

Thanks Nic,

we intend to trial the upgrade on a 'Development' server first, then repeat the process on our Prod system out of hours.

But yes I will be taking your suggestion to do that trial a few times over !



Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

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...

2,770 views 18 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you