JIRA Upgrade from 6.3.1 to 7.6.1

Alla Sasi Kanth January 16, 2018

We currently have JIRA applications (v6.3.1) running on DEV, QA and PROD environments. We are planning to upgrade all the 3 JIRA instances to 7.6.1.

All 3 environments are on Linux servers.

These JIRA applications are connected to CROWD, CRUCIBLE and FISHEYE. Before JIRA upgrade, we are supposed to upgrade the CROWD, CRUCIBLE and FISHEYE applications.

Is there any straight forward approach to upgrade JIRA from 6.3.1 to 7.6.1 ? Any documentation if provided would be appreciated. 

 

Thanks in advance.

1 answer

1 vote
somethingblue
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 18, 2018

Hi Alla,

If you are not running JIRA Service Desk the upgrade is fairly straightforward, however, there is a caveat involving 7.1:


Upgrading to JIRA Software 7.1

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 the latest version of JIRA Software 7.0.x first. We recommend the following upgrade path:

JIRA + JIRA AGILE  JIRA SOFTWARE 7.0JIRA SOFTWARE 7.1 (latest version)

(info) The recommended, intermediary upgrade version is necessary due to upgrade tasks that were removed in JIRA Software 7.1.0.

As an alternative, you can upgrade to an intermediary version of JIRA Agile (any version above, and including, 6.4.5), which includes the upgrade tasks that were removed.

Once that is complete you can go to 7.6.x.

If you are using JIRA Service Desk the upgrade path is a bit more complicated:

If you already have JIRA Service Desk

  • Make sure you have at least JIRA Service Desk 3.0 and JIRA 7.0
  • If you don't have JIRA Service Desk 3.0 or JIRA 7.0, first upgrade to JIRA Service Desk 3.0 and JIRA 7.0. Then, upgrade to JIRA Service Desk 3.2 and JIRA 7.2.

Hopefully that clears things up a bit.  Before upgrading I would also follow the advise in Checking add-on compatibility with application updates to make sure your add-ons will still be compatible in the newer version.

Cheers,

Branden

Suggest an answer

Log in or Sign up to answer