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

Cannot import Jira backup into Cloud because of wrong version in backup file

    XMLWordPrintable

Details

    Description

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

      Summary

      Cannot migrate from server to cloud because the minimum required version is 3.0.0, but the backup file is exported from Service Desk 3.2.0. 

      Steps to Reproduce

      1. Upgrade to Service Desk 2.5.9 to 3.2.0
      2. Backup data
      3. Import backup file to cloud instance

      Expected Results

      Import data successfully.

      Actual Results

      Cannot import data and received this message:

      We can't complete your upgrade. It looks like the data you are trying to import is from an earlier version of JIRA Service Desk. You need to upgrade to JIRA Service Desk 3.0 first, then export new data and try again. Read these upgrade notes for instructions: http://confluence.atlassian.com/migration/jira-7/server_jira+jsd_upgrade

       

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JSDSERVER-4272 Importing JIRA Service Desk Server site export into JIRA Cloud fails with version error

          • Medium - Medium priority issues
          • Gathering Impact
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JSDCLOUD-4766 Cannot import Jira backup into Cloud because of wrong version in backup file

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              vtruong Vu 🎧
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync