JIRA Software 7.2.x upgrade notes

Before you begin

Sometimes we find out about a problem with the latest version of JIRA Software after we have released the software. In these cases, we publish information about the known issues in the Jira Software knowledge base. Please check for known issues and follow the instructions as necessary.

What do I do if I have problems with JIRA Software?

If you have problems when installing/upgrading JIRA Software or using it after an upgrade, please contact our support teamThis is the fastest way to get your problems addressed. The support team can work with you to figure out what is going wrong, and if there is a bug with JIRA Software, they will escalate it to our development team. 

Please follow the instructions in the general Upgrading Jira applications guide, as well as the JIRA Software 7.2.x specific instructions below. The general guide contains important tasks that are essential for getting your upgraded JIRA installation to work correctly and, if necessary, migrating existing configurations.

Also, please make sure that your licenses and add-ons are all up-to-date. Removing any incompatible add-ons before upgrading may help you avoid problems during your upgrade process. You can check the compatibility of your add-ons before your upgrade using the JIRA update check.

This page also describes known issues as well as changes you should be aware of before deciding whether or not to upgrade to JIRA Software 7.2.x.

On this page:

Upgrading to JIRA Software 7.2

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)

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

See the Migration Hub for more information on upgrading to JIRA Software 7.0.

To upgrade from JIRA Software 7.0 to JIRA Software 7.2, please see Upgrading Jira applications.

Please read JIRA Software 7.0.x release notes and JIRA Software 7.1.x release notes.

In addition to this upgrade path, please read the Upgrade Notes for every version of JIRA Agile you are skipping.

Information for JIRA developers

See Preparing for 7.2 for important information that could affect your add-ons or scripts. Also, see our Java API policy for JIRA.

Information for administrators

Optimizing the upgrade process

When you start the upgrade, JIRA automatically creates an XML backup of your database, which slows down the upgrade process. Since you’re creating your own backup anyway, you can disable the automatic backup before the upgrade.

  1. Stop JIRA.
  2. Edit the jira-config.properties file, located at the root of your JIRA home directory.
    (info) If this file doesn't exist, create it in a text editor. For more info, see Making changes to the jira-config.properties file.
  3. Add the following entry:

    jira.autoexport=false
  4. Start JIRA.

Performance issues

We’ve noticed that versions 7.2.9 and 7.2.10 have performance issues and show errors while opening pages or finishing some actions. This applies only if you’re using postgreSQL and have more than 500k users. To work around it, increase the heap size by 1GB per million users. We’ll release a fix for this in the next bugfix release.


Upgrading from earlier versions

Upgrading from a 7.1 or later version - There are no known issues

Upgrading from a 7.0.x version - There is a known issue regarding gadgets, and there is a workaround described in the JIRA Software 7.1.x upgrade notes.

Upgrading from a version earlier than 7.0 - Please consult the Migration hub as it contains information on important user management, application access and log in changes. 

Last modified on Feb 23, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.