Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-291

Duplicated Workflows in the backup file causes import to fail

    XMLWordPrintable

    Details

    • Support reference count:
      19
    • Symptom Severity:
      Severity 3 - Minor
    • UIS:
      1

      Description

      Summary

      When importing to the Cloud, the import fails on the validation stage with this error:

      Import error
      
      There was an error importing file jira-export (4).zip: Validation failed. Following issues were reported:
      Cannot complete the import because one of the import files contains the following duplicate workflows: 'workflow 1'. Search the Atlassian Administrator Knowledge Base for instructions on how to fix this, or contact Atlassian Support for help.
      

      This happens when there are Workflows with the same name in the Backup file. By right, workflows may not have the same name; Jira will not allow this through the UI. However, if the Workflow names has the same name but with different letter case, for example:

      • "workflow 1"
      • "WORKFLOW 1"

      Jira will allow this to happen. However, generating a backup, and restoring this to a Cloud instance will fail on the validation stage.

      Steps to Reproduce

      1. Create two Workflows, they may remain Inactive.
      2. Rename the first workflow as "workflow 1".
      3. Rename the second workflow also as "workflow 1".
        • Notice that Jira does not allow the second workflow to has the same name
      4. Proceed to rename the second workflow to "Workflow 1". This should go through.
      5. Now, generate a backup, and use this to import to a Cloud instance.

      Expected Results

      The import should go through, as Jira seems to allow the same workflow name but with different casing.

      Actual Results

      The import fails on the validation stage:

      Notes

      1. This can also be resolved by not allowing the same workflow name but with different casing.
      2. This affects both, Cloud to Cloud, and Server to Cloud.
      3. There might also be occurrences where the duplicated workflow has the same name with the same casing, however, it is currently unknown on how it gets to this state.

      Workaround

      Delete or Rename one of the duplicate workflow on the Source instance, generate a new backup, and use the new backup to import.

        Attachments

        1. screenshot-1.png
          screenshot-1.png
          52 kB
        2. screenshot-2.png
          screenshot-2.png
          98 kB

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              msatriya Sadiq (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              18 Start watching this issue

                Dates

                Created:
                Updated: