Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-44010

Importing JIRA Cloud to JIRA Server 6.4.7 Fails

XMLWordPrintable

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

      Problem Description

      Importing backup into from JIRA Cloud to JIRA Server fails

      Environment

      Cloud backup generated on 2015/06/24 (JIRA-backup-20150624)

      Expected Behavior

      Restore process should be successful from Cloud XML back to JIRA Server

      Actual Behavior

      Restore process fails with the below error in the UI

      The file you are trying to import is from JIRA 6.5-OD-07-005, which is newer than your current version of JIRA and will not work. The import file claims it can be successfully imported into JIRA 6.3.12 or later.

If JIRA 6.3.12 is not yet available for download, please contact support.

      This might be due to change of downgrade logic in 6.4.6.

      Workaround

      Try to restore the XML back up from the Cloud on fresh copy of JIRA 6.4.5
      Enter the license when you restore it on JIRA 6.4.5

        1. importerror.png
          importerror.png
          18 kB
        2. JIRA_645_workaround .png
          JIRA_645_workaround .png
          51 kB

            [JRACLOUD-44010] Importing JIRA Cloud to JIRA Server 6.4.7 Fails

            Ben Magro (Inactive) added a comment -

            This issue is duplicated by https://jira.atlassian.com/browse/JRA-43767. A fix will be deployed in the next Cloud release. A workaround can be found at the attached issue link.

            Thanks,
            Ben Magro
            Service Enablement

            Ben Magro (Inactive) added a comment - This issue is duplicated by https://jira.atlassian.com/browse/JRA-43767 . A fix will be deployed in the next Cloud release. A workaround can be found at the attached issue link. Thanks, Ben Magro Service Enablement

            Mauricio Herrera added a comment - - edited

            I have the same problem but this fix NOT works for me.

            "You are attempting to import data from JIRA 6.5-OD-07-005 which is a more recent version than this version. Some features that you may have used before will not be available in this version of JIRA"

            Jira version 6.4.7 32bits

            Mauricio Herrera added a comment - - edited I have the same problem but this fix NOT works for me. "You are attempting to import data from JIRA 6.5-OD-07-005 which is a more recent version than this version. Some features that you may have used before will not be available in this version of JIRA" Jira version 6.4.7 32bits

            Syed Irtaza Ali added a comment -

            As Sachin mentioned in the above comment,

            I edited entities.xml file, and searched for text (Ctrl + F)
            upgradeclass="com.atlassian.jira.upgrade.tasks.UpgradeTask_Build65001" targetbuild="65001" status="complete"

            I added this attribute downgradetaskrequired="N" and the import worked fine.

            The node should look something like this,
            <UpgradeHistory id="10020" upgradeclass="com.atlassian.jira.upgrade.tasks.UpgradeTask_Build65001" targetbuild="65001" status="complete" downgradetaskrequired="N"/>

            Syed Irtaza Ali added a comment - As Sachin mentioned in the above comment, I edited entities.xml file, and searched for text (Ctrl + F) upgradeclass="com.atlassian.jira.upgrade.tasks.UpgradeTask_Build65001" targetbuild="65001" status="complete" I added this attribute downgradetaskrequired="N" and the import worked fine. The node should look something like this, <UpgradeHistory id="10020" upgradeclass="com.atlassian.jira.upgrade.tasks.UpgradeTask_Build65001" targetbuild="65001" status="complete" downgradetaskrequired="N"/>

            Sam Omidi (Inactive) added a comment -

            Hi sapendse

            Thanks for your comment, which version(s) of JIRA you have tried it on?

            Cheers,
            Sam

            Sam Omidi (Inactive) added a comment - Hi sapendse Thanks for your comment, which version(s) of JIRA you have tried it on? Cheers, Sam

            Sachin Pendse added a comment -

            Hey Mark and Sam,

            I think I have a fix for your issue! Check out Marcin Kempa's answer here — we did the same fix, and it worked for us (we were having the same issue as you).

            https://jira.atlassian.com/browse/JRA-42797

            Go to the entities.xml file, and Ctrl + F "upgradeclass="com.atlassian.jira.upgrade.tasks.UpgradeTask_Build65001" targetbuild="65001" status="complete"" and then add ""downgradetaskrequired="N"" at the end, and then it will work!

            Sachin Pendse added a comment - Hey Mark and Sam, I think I have a fix for your issue! Check out Marcin Kempa's answer here — we did the same fix, and it worked for us (we were having the same issue as you). https://jira.atlassian.com/browse/JRA-42797 Go to the entities.xml file, and Ctrl + F "upgradeclass="com.atlassian.jira.upgrade.tasks.UpgradeTask_Build65001" targetbuild="65001" status="complete"" and then add ""downgradetaskrequired="N"" at the end, and then it will work!

              Unassigned Unassigned
              somidi Sam Omidi (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: