• Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Medium Medium (View bug fix roadmap)
    • None
    • 5.0, 5.0.3, 5.0.6, 5.2.7
    • None

      Project Import failed even with Plugin installed in both Source and Target Instance.

      Step to reproduce the error:

      1. Install Greenhopper plugin on JIRA instance A using the UPM.
      2. Install Greenhopper plugin with the same version on JIRA instance B using the UPM.
      3. Create a project X on instance A
      4. Backup instance A
      5. Delete project X from A
      6. Restore project X to JIRA instance B. It fails as shown in screenshot.

      This step will not reproduce the error:

      1. Install Greenhopper plugin on JIRA instance A using the UPM.
      2. Install Greenhopper plugin with the same version on JIRA instance B using the UPM.
      3. Restart JIRA instance A
      4. Create a project Y on instance A
      5. Backup instance A
      6. Delete project Y from A
      7. Restore project Y to JIRA instance B. It succeeds.

      This is tested in JIRA 5.0.3.

            [JRASERVER-28391] Project Import Fail With Error Requires Custom Field

            Ivan Tse added a comment -

            I've had to go quite a bit farther to get the through the custom field errors to not appear. The process I've had to take is outlined in the KB I've written below.

            https://confluence.atlassian.com/display/JIRAKB/Project+Import+Error

            Ivan Tse added a comment - I've had to go quite a bit farther to get the through the custom field errors to not appear. The process I've had to take is outlined in the KB I've written below. https://confluence.atlassian.com/display/JIRAKB/Project+Import+Error

            metapoint added a comment -

            jalbion Thank you much clearer. So the restart is required? interesting.

            metapoint added a comment - jalbion Thank you much clearer. So the restart is required? interesting.

            metapoint added a comment -

            jalbion Your instructions aren't exactly clear as both project X and Y appear to be backed up and restored the same way on the same instance.

            metapoint added a comment - jalbion Your instructions aren't exactly clear as both project X and Y appear to be backed up and restored the same way on the same instance.

              Unassigned Unassigned
              jalbion Janet Albion (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: