Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management 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

    • 4
    • 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.

      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

            [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

            Ishwinder Kaur made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Ishwinder Kaur added a comment - - edited
            Atlassian Update - 03 March 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion has had very low engagement over the past four years, with no new watchers, votes, or comments. As a result, we're closing it for now.

            We understand that this suggestion might still be important to you. If you'd like to provide additional context or information about why it remains relevant, please contact our Technical Support team for assistance. We'll be happy to review your feedback.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.

            Kind regards,
            Jira Service Management Data Center

            Ishwinder Kaur added a comment - - edited Atlassian Update - 03 March 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion has had very low engagement over the past four years, with no new watchers, votes, or comments. As a result, we're closing it for now. We understand that this suggestion might still be important to you. If you'd like to provide additional context or information about why it remains relevant, please contact our Technical Support team for assistance. We'll be happy to review your feedback. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues , current work, and future plans. Kind regards, Jira Service Management Data Center
            Ishwinder Kaur made changes -
            Labels Original: affects-server affects-upgrade pse-request ril New: affects-server affects-upgrade cleanup-seos-fy25 pse-request ril
            SET Analytics Bot made changes -
            UIS Original: 5 New: 4
            Conny Postma made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 237217 ]
            Marc Dacanay made changes -
            Labels Original: affects-server affects-upgrade pse-request New: affects-server affects-upgrade pse-request ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 976701 ]
            SET Analytics Bot made changes -
            UIS Original: 3 New: 5
            SET Analytics Bot made changes -
            UIS Original: 5 New: 3
            SET Analytics Bot made changes -
            UIS Original: 4 New: 5

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

                Created:
                Updated:
                Resolved: