How to upgrade jira 4.4.4 with GreenHopper 5.8.4 to last Jira with Agile

ibud developers March 2, 2017

How to upgrade jira 4.4.4 with GreenHopper 5.8.4 to last Jira with Agile.

When i tried to export data from old JIRA via xml I recived the following message in  log file

"Upgrade failed: This version of JIRA Agile requires a minimum build number of #45 in order to proceed. The latest upgrade task to have been successfully completed is #14. You must uninstall this version of JIRA Agile and attempt an upgrade via an intermediary version."

2 answers

1 accepted

3 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 2, 2017

There's no chance of jumping to 7 from 4.

You need to go from 4.4 to 6.0 (possibly via 5.2), then 6.0 to 6.14, then you'll be able to go to 7.3.  During each jump up to 6.14, you'll need to upgrade to the right version of Greenhopper, then Agile, and then move to JIRA Software when going up to 7. 

See https://confluence.atlassian.com/adminjiraserver073/upgrading-jira-applications-861253088.html

Niclas Sandstroem
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.
March 2, 2017

If other stumble on this subject there is some minor issues jumping from JIRA 6.4 to JSW 7.2 or 7.3 with JIRA Service Desk. So if you do this with JSD go through JSW 7.0 and upgrade to JSD 3.0

Good luck!

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 2, 2017

There are known limitations with trying to jump this many versions at once.   We first saw this with any JIRA Agile 6.3.xx.x versions that tried to upgrade to JIRA Software 7.1.x versions.  https://confluence.atlassian.com/jirakb/this-version-of-jira-agile-requires-a-minimum-build-number-of-45-in-order-to-proceed-812222943.html explains the current error you are seeing.   The newer releases simply don't have the upgradetasks needed to upgrade data from such an old version of JIRA.

Atlassian support actually recommend going to 7.0.x before you try any other higher JIRA 7 verisons like 7.1, 7.2, etc.  The general outline for situations like this is explained in https://confluence.atlassian.com/adminjiraserver071/skipping-major-versions-when-upgrading-jira-applications-802592265.html

I would recommend going to 6.0.x first, then 6.4.x, then 7.0.x.   From that version you should be able to upgrade directly to any JIRA 7.2.x or 7.3.x release.   But Nic is right, it is important to make sure that you load that Agile/Greenhopper plugin that is compatible with those versions in each upgrade of JIRA to make sure this can upgrade your Agile data properly.

Suggest an answer

Log in or Sign up to answer