Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-47764

Importing from JIRA cloud to JIRA server fails

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Low
    • None
    • None
    • None

    Description

      Summary

      Importing from JIRA cloud to JIRA server 7.0.4 fails with error 'jira software is currently unavailable. This might be because an upgrade task has failed to run or has not yet completed'. Reinstalling JIRA software does not fix the issue.

      Environment

      JIRA server 7.0.4

      Steps to Reproduce

      1. Get backup of cloud instance
      2. Install latest version of jira 7.0.4
      3. Run XML import which completes without error.
      4. On first run of jira you receive the message jira software is currently unavailable. This might be because an upgrade task has failed to run or has not yet completed.

      Expected Results

      JIRA to launch without error

      Actual Results

      JIRA launches with error and JIRA Software does not work

      JIRA Agile v7.0.1-D20150831T075251 (a8911e5beba95691) started at 07 Sep 2015 01:58

      JIRA Agile v7.0.2-D20150904T042837 (c3fc2e3787bad862) started at 14 Sep 2015 01:27

      JIRA Agile v7.0.3-D20150914T124347 (7e76d8d76870cd63) started at 21 Sep 2015 01:19

      JIRA Agile v7.0.4-D20150923T101309 (58e240c5cc26afe4) started at 28 Sep 2015 03:49

      JIRA Agile v7.1.0-D20151020T142903 (3d19d53432899181) started at 26 Oct 2015 01:33

      JIRA Agile v7.1.2-D20151028T015626 (f4e785ae6fe458a1) started at 02 Nov 2015 01:53

      JIRA Agile v7.1.4-D20151111T031543 (0d6026ddf635f7e1) started at 16 Nov 2015 12:38

      JIRA Agile v7.1.6-D20151117T003834 (2f84d577cde6ef35) started at 23 Nov 2015 12:11

      JIRA Agile v7.1.7-D20151125T224928 (dfe715220fd03e9c) started at 30 Nov 2015 12:12

      JIRA Agile v7.1.8-D20151201T145156 (d7cf536d7ae17636) started at 07 Dec 2015 02:07

      *JIRA Agile v7.0.6 (c8e6505a72e83124) started at 08 Dec 2015 01:23

      Notes

      Workaround

      UPDATE propertynumber SET propertyvalue = 48
      WHERE id = (SELECT id FROM propertyentry WHERE property_key = 'GreenHopper.Upgrade.Latest.Upgraded.Version');
      UPDATE propertystring SET propertyvalue = '48'
      WHERE id = (SELECT id FROM propertyentry WHERE property_key = 'com.pyxis.greenhopper.jira:build');

      original issue: https://support.atlassian.com/browse/GHS-27367

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              schristopher@atlassian.com ScottC
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: