Upgrade to version 7.2x of Jira server

Still need help?

The Atlassian Community is here for you.

Ask the community

This article only applies to Atlassian's server products. Learn more about the differences between cloud and server.

Purpose

To help provide a detailed guide to help with the upgrade process of large scale and business critical JIRA environments to JIRA 7.2.latest. Other methods for upgrade also exist, see here: Upgrading JIRA applications

Preparation

Before You Start

  • Check JIRA 7.2 Supported Database Versions:
    • Oracle 12c
    • MySQL 5.5, 5.6
    • PostgreSQL 9.2, 9.3, 9.4
    • Microsoft SQL Server 2012, 2014
  • Check plugin compatibility
    • Within your current installation of JIRA, go to Administration > Add-ons > Manage add-ons. At the bottom of the page, there is a link for JIRA update check.

    • Third-party plugins may have upgrade requirements, please ensure to be familiar with these requirements as it may require additional intermediate upgrade steps
  • Check other Atlassian product compatibility, see Application links version matrix. JIRA 7.2 uses AppLinks 5.2.3, based on that, minimal versions for JIRA 7.2 for other applications:
    • Bamboo 5.10+
    • Confluence 5.6+
    • Crucible/Fisheye 3.6+

    • Stash 3.4+
  • Review the Recommended Readings (links to the right)

Optimizing the Upgrade Process

These steps will help reduce the amount of time needed for the full upgrade process to complete

  • Disable Upgrade Index and Automated Upgrade Backup

  • (For JIRA <= 7.2.7) Apply the workaround for JRA-61383. In large installations the upgrade rename of "Agile" fields to "Software" increases the length of your outage. Doing this via SQL is fast and low risk so long as you test your upgrade procedure in advance.

Testing

We strongly recommend performing your upgrade in a test environment first. Do not upgrade your production JIRA server until you are satisfied that your test environment upgrade has been successful. If you have any problems with your test environment upgrade which you cannot resolve, create an issue at our support site so that we can assist you.

Details: Establishing staging server environments for JIRA applications.

On this page




Upgrade Steps for JIRA Software

Before Proceeding

  • Using JIRA Agile ? - Ensure to first upgrade the JIRA Agile add-on to the latest version compatible with your version of JIRA. JIRA Agile version must be 6.4.5 or greater before proceeding.
  • Using JIRA Service Desk? - Ensure to first upgrade to JIRA to version 7.0 and JIRA Service Desk to version 3.0 (or later in the 7.0.X and corresponding 3.0.X range)

  • Third-party plugins may have upgrade requirements, please ensure to be familiar with these requirements as it may require additional intermediate upgrade steps

Supported Database Versions:

  • Oracle 12c
  • MySQL 5.5, 5.6
  • PostgreSQL 9.2, 9.3, 9.4
  • Microsoft SQL Server 2012, 2014

Upgrading to JIRA Software 7.0.latest

Required if upgrading from  JIRA 6 with Service Desk. Skip to next section if not using Service Desk.
  1. Stop the current JIRA instance
  2. Make a copy of the JIRA database to a new database
  3. Make a copy of the JIRA_HOME to a new location
  4. Please check that all JIRA bundled plugins are enabled (eg: jira-importers-plugin). Check pluginstate table. 
  5. Remove the plugins/ folder located in the new JIRA_HOME
    1. Performing the upgrade without plugins has been found to be more reliable and faster
    2. If you run JIRA DataCenter, also remove (and backup) <Shared>/plugins/ folder 
  6. Modify the dbconfig.xml file in the newly copied JIRA_HOME
    1. Configure the file to point to the newly copied database
  7. Download the latest JIRA Software 7.0.x Archive version
  8. Extract the JIRA Software 7.0.latest archive to a new target JIRA_INSTALL folder
  9. Configure your JIRA Home folder path and point to the newly copied JIRA_HOME
  10. Create a jira-config.properties file in your JIRA Home folder (Edit the jira-config.properties file in Jira server) and add the options below:

    upgrade.reindex.allowed=false
    jira.autoexport=false
    1. If the file already exists, simply add these lines to the start of the file
    2. These parameters will disable the automated upgrade backup and automated index after upgrade
  11. Copy memory allocation settings and any other custom parameters you deem necessary from the previous installation to the new one, as described in Setting properties and options on startup
  12. Start JIRA and review the logs to ensure the upgrade completed successfully.
  13. Navigate to Cog Icon > Applications > Version & Licenses.
  14. Click on Install in the JIRA Service Desk application. This should install version 3.0.11
  15. Re-install plugins via the Cog Icon > Add-ons > Find new add-ons
    1. If prefered, upload the add-ons manually via Cog Icon > Add-ons > Manage add-ons > Upload add-on

      Not all plugins are compatible with JIRA 7.2.latest. Ensure to verify compatibility first!
  16. Test and ensure that the instance is functioning to satisfaction
    1. Perform a 
  17. Proceed to next section for upgrading to 7.2.latest

Upgrading to JIRA Software 7.2.latest

  1. Stop the current JIRA instance
  2. Make a copy of the JIRA database to a new database
  3. Make a copy of the JIRA_HOME to a new location
  4. Remove the plugins/ folder located in the new JIRA_HOME
    1. Performing the upgrade without plugins has been found to be more reliable and faster
    2. If you run JIRA DataCenter, also remove (and backup) <Shared>/plugins/ folder 
  5. Modify the dbconfig.xml file in the newly copied JIRA_HOME
    1. Configure the file to point to the newly copied database
  6. Download JIRA Software 7.2.latest Archive version
  7. Extract your JIRA Software 7.2.latest to a new target JIRA_INSTALL folder
  8. Configure your JIRA Home folder path and point to the newly copied JIRA_HOME
  9. Create a jira-config.properties file in your JIRA Home folder (Edit the jira-config.properties file in Jira server) and add the options below:

    upgrade.reindex.allowed=false
    jira.autoexport=false
    1. If the file already exists, simply add these lines to the start of the file
    2. These parameters will disable the automated upgrade backup and automated index after upgrade
  10. Copy memory allocation settings and any other custom parameters you deem necessary from the previous installation to the new one, as described in Setting properties and options on startup
  11. Start JIRA and review the logs to ensure the upgrade completes successfully
  12. If using Service Desk, navigate to Cog Icon > Applications > Version & Licenses
    1. Update/Install the JIRA Service Desk application to the latest version
  13. Re-install plugins via file the Cog Icon > Add-ons > Find new add-ons
    1. If prefered, upload the add-ons manually via Cog Icon > Add-ons > Manage add-ons > Upload add-on

      Not all plugins are compatible with JIRA 7.2.latest. Ensure to verify compatibility first!
  14. Test and ensure that the instance is functioning to satisfaction
  15. Restart JIRA
  16. Perform a 


Bugs Fixed in JIRA Software 7.2

Quick expand

Key Summary P Status
Loading...
Refresh

Suggestions Implemented in JIRA Software 7.2

Quick expand

Key Summary P Status
Loading...
Refresh

Login to  https://jira.atlassian.com  to enable display of issue details below.

Known Problems

Problem Workaround
JSD-4220 - Getting issue details... STATUS
This is a one-time occurrence until JIRA is restarted.
JSD-4239 - Getting issue details... STATUS
Upgrade to JIRA 7.0.latest + Service Desk 3.0.11 before then upgrading to JIRA 7.2.latest.
JRA-62669 - Getting issue details... STATUS
Access the index admin page and use the Copy the Search Index from another node functionality.
JRA-63239 - Getting issue details... STATUS
The workaround is to modify the export URL and set a value. Please refer to the bug report for full details.
JRA-63189 - Getting issue details... STATUS

Currently, Structure Plugin has been identified to be able to prevent JIRA Data Center from locking the index. The structure has fixed this as of v3.3.3, please upgrade.

JRA-61383 - Getting issue details... STATUS
Workaround is to update the changes in the JIRA database before upgrading. Please refer to the bug report for full details.
FIXED as of JIRA Software 7.2.8
JSW-13355 - Getting issue details... STATUS
The problem is due to querying for unarchived versions. Ensure to archive any versions that are not actively used by the system to help improve speeds.
Managed Sprints Permission Users may experience Sprint permissions issues as JIRA introduced the "Manage Sprints" permission. This may result in users noticing the inability to perform Sprint actions. If problems arise, please check the permissions for users:
JSW-13530 - Getting issue details... STATUS

Re-index JIRA.
FIXED as of JIRA Software 7.2.7

JRA-61007 - Getting issue details... STATUS

Using database native backup tools when creating backups. If it is required that JIRA can generate backup XMLs, use the Oracle 11g driver.
FIXED as of JIRA Core 7.2.7

JRASERVER-60604 - Getting issue details... STATUS
Update bundled Oracle driver from 12.1.0.1 to 12.2.0.1 version
JRASERVER-64095 - Getting issue details... STATUS
See workaround section in the ticket.
JRASERVER-29310 - Getting issue details... STATUS
See workaround section in the ticket.
Description To help provide a detailed guide to help with the upgrade process of large scale and business critical JIRA environments to JIRA 7.2.latest. Other methods for upgrade also exist, see here: Upgrading JIRA applications
Product Jira
Platform Server



Last modified on Sep 25, 2019

Was this helpful?

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