Jira upgrade fails with error minimum build number of 45 required
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
The workaround in this article is valid only for the versions specified. It is not valid for upgrades to later versions. For new Jira versions please refer to Jira software installation on top of Jira core fails with a minimum build number of 45.
Problem
When upgrading your instance to JIRA 7.1.0
The following appears in the atlassian-jira
.log
1
2
3
[c.a.s.core.upgrade.PluginUpgrader] 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 #24. You must uninstall this version of JIRA Agile and attempt an upgrade via an intermediary version.
java.lang.IllegalStateException: 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 #24. You must uninstall this version of JIRA Agile and attempt an upgrade via an intermediary version.
at com.atlassian.greenhopper.upgrade.AbstractGhUpgradeTask.checkMinimumDataRequirement(AbstractGhUpgradeTask.java:95)Diagnosis
Diagnostic Steps
Verify from the logs, if the JIRA Agile is older than JIRA AGILE 6.4.0 prior to the upgrade:
1 2 3 4 5 6 7JIRA Agile Run History JIRA Agile v5.10.5.1 (e6c4c0932fc2) started at 13 Jul 2012 10:56 JIRA Agile v6.0.2 (5867fd92d6a2) started at 03 Sep 2012 01:51 *JIRA Agile v7.1.18 (12a20403398fa394) started at 24 Feb 2016 04:25In above example, the JIRA Agile is on 6.0.2 prior to upgrade to 7.1.0
Cause
Upgrade task 45 was introduced in JIRA Agile 6.4.0. As a result, Agile versions that are older than 6.4.0 cannot upgrade directly to Agile 7.1.0. It must upgrade to an intermediary version in the range of 6.4.0 and 6.7.x (our latest 6.7.x release is 6.7.16). This is tracked under JSWSERVER-12792 - Importing from Server to Cloud or Upgrading to JIRA 7.1.0 from Agile earlier than build 45 is causing errors.
Solution
Workaround
Navigate to your
<JIRA_HOME>/plugins/installed-pluginsfolder and move the jira-greenhopper-plugin-7.x.y.jar file to a temporary location (the exact version of this plugin depends on what version of JIRA you upgraded to). Make a note of what that location is since you will need it later.Download the latest JIRA Software 7.0.x obr file from this location: https://marketplace.atlassian.com/download/plugins/com.atlassian.jira.jira-software-application/version/700010.
Unpack the obr file and grab the jira-greenhopper-plugin-7.0.10.jar file from the dependencies folder.
Place the jira-greenhopper-plugin-7.0.x.jar file in your
<JIRA_HOME>/plugins/installed-pluginsfolder.Restart JIRA. This will run your Agile data through the necessary upgrade tasks. When JIRA comes back up, you should be able to access Boards, etc.
Navigate to Administration > Add Ons > Manage Ons and upload the jar file in step 1 from its temporary location using the Upload add-on link near the top of the page.
Resolution
Upgrade JIRA to 6.4, and install JIRA Agile 6.7.16.
Upgrade that instance to 7.0.X then to the target version.
Additional details on upgrade task requirements can be found in the Upgrade Notes And the following Upgrade Guide
If you're using JIRA and JIRA Agile, and you want to upgrade to the latest version of JIRA Software, we recommend you upgrade to JIRA Software 7.0 first. We recommend the following upgrade path:
JIRA + JIRA AGILE→JIRA SOFTWARE 7.0→ JIRA SOFTWARE 7.2→ (latest version)
Always make sure to review the Release notes and Upgrade notes for all major version between your current and desired version before performing an upgrade
Was this helpful?