What is the minimum version of JIRA required for the current version of JIRA Service Desk ?

[Barry O'Neill]

What is the minimum version of JIRA required for the current self-hosted version of JIRA Service Desk ?

Are additional licenses required to hook one into the other ?

Thanks,

Barry O'Neill

Instantel

[somethingblue · Accepted solution]

Hi Barry,

For the latest version of JIRA Service Desk (3.10.1) you will need JIRA 7.7 per the JIRA applications compatibility matrix and the JIRA Service Desk 3.10.x upgrade notes:

Upgrade notes

Priority schemes (UI changes)

We've made significant changes to how priorities are managed in JIRA. Currently, your JIRA Service Desk projects are using a global list of priorities. After the upgrade, all these priorities will be moved to the default priority scheme, which works in the same way. Moreover, you can create new priority schemes and make use of them in JIRA Service Desk projects.

Account verification emails

Currently, for organizations running email-based service desks, account verification emails are sent out to customers when requests are raised by email. After the upgrade, project administrators can now disable these account verification emails.

Upgrade procedure

Note: Upgrade to a test environment first. Test your upgrades in your test environment before rolling them into production.

If you're already running a version of JIRA, please follow these instructions to upgrade to the latest version:

1. Before you upgrade, we strongly recommend that you back up your installation directory, home directory, and database.
2. Read the release notes and upgrade guides for all releases between your version and the latest version.
3. Download the latest version of JIRA Service Desk.
4. Follow the instructions in the Upgrade Guide.

Upgrading from earlier versions?

• 7.0, or laterTake a look at the upgrade matrix. It lists known issues you should be aware of when upgrading between multiple versions.

• Earlier than 7.0Consult the Migration hub. The JIRA 7.0 release introduced significant changes. You must first upgrade to JIRA 7.0 before upgrading to later versions.

Hopefully that helps!

Cheers,

Branden

[Barry O'Neill]

We're on JIRA 6.2.7

...so I guess there would be a few hoops to jump through to get it compliant with a new install of Service Desk.

[Nic Brough -Adaptavist-]

Yup.  Upgrade it to 6.4, then 7.0, then 7.7.

[Barry O'Neill]

Does the database get "massaged" with each upgrade ? Just wondering if you could take JIRA 7.7 on a new machine and plop in the database from our old 6.4 box 

[Nic Brough -Adaptavist-]

Yes, it changes the shape of the data.  You can't just point a 7.7 at a 6.4 database.

[somethingblue]

Hi Barry,

Most likely not because JIRA 6.4 and JIRA 7.7 have differing requirements when it comes to the Supported platforms, e.g. database versions.

Take a look at the Supported platforms page for JIRA 7.7 and compare it to the Supported platforms for JIRA 6.4 and make sure you have the correct database version and then you can use the JIRA application configuration tool to connect the old data to the new installation of JIRA.

Cheers,

Branden

[Barry O'Neill]

Once the process starts, I guess there is no roll-back mechanism in the event of failure ?

[somethingblue]

Hi Barry,

Since you'll be performing a stepped upgrade you can create a backup at each step of the upgrade that is successful and roll back to that point if necessary:

Prior to rolling back your JIRA application upgrade, ensure that you have the following backups from your previous application version:

• The JIRA application database (generated by your database's own backup tools).
• The JIRA application Home Directory.
• The JIRA application Installation Directory.

If you do get to a point you need to roll back take a look at the Rolling back a JIRA application upgrade knowledge base article for the rollback procedures

Cheers,

Branden

[Barry O'Neill]

Thanks for the info !

[Barry O'Neill]

Thanks for the info !