Uploaded image for project: 'Jira Service Management Server and Data Center'
  1. Jira Service Management Server and Data Center
  2. JSDSERVER-4239

As a JIRA Service Desk administrator, I would like to be able to upgrade from JSD 2.5.9 to 3.2 directly

    XMLWordPrintable

Details

    • 6
    • 32
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Problem Definition

      As per the JIRA Service Desk 3.2.x Release Notes, it is currently not possible to upgrade directly from JIRA 6.4.x and Service Desk 2.5.9 to JIRA Core 7.2.x with JIRA Service Desk 3.2.x. Hence, customers running on JIRA 6.4.x will have to upgrade twice, increasing their downtime and also the upgrade effort to go to JIRA 7.2.x and JSD 3.2.x.

      Suggested Solution

      As a JIRA administrator, I would like to be able to upgrade from JIRA 6.4.x and JSD 2.5.9 to JIRA 7.2 and JIRA Service Desk 3.2 directly so that I can perform a single upgrade.

      Workaround

      The following jira-config.properties parameters can be used when upgrading from JIRA 6.4 to 7.0 and Service Desk 3.0:

      upgrade.reindex.allowed=false
      jira.autoexport=false
      

      This will cause the intermediate upgrade path ( JIRA 6.4 -> JIRA 7.0 -> JIRA 7.2 ) to occur much faster as JIRA performs an export and re-index normally as part of the upgrade which takes a long time in larger environments and is unnecessary for intermediate upgrade versions. These parameters can be removed when upgrading JIRA 7 to JIRA 7.2

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              dconrad Danilo Conrad
              Votes:
              9 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated:

                Backbone Issue Sync