Doing a C2C migration causes the target default priority scheme to be modified with unexpected priorities added to it

XMLWordPrintable

    • 4
    • Minor
    • Jira Software

      Issue Summary

      Doing a C2C migration causes the target default priority scheme to be modified.

      Steps to Reproduce

      1. Create two separate Jira Cloud sites
      2. On the source site, modified the default priority scheme that gets generated out of the box
      3. Create a Jira company-managed project
      4. Associate the modified default permission scheme to the project
      5. Migrate the project using the Copy product data

      Expected Results

      The default priority scheme that exists on the target site should remain intact, and the incoming default priority scheme from the source site should be created.

      Actual Results

      The existing default priority scheme on the target will receive all the priorities from the incoming priority scheme.

      Images

      Source Target After Migration

      Workaround

      Adjust the priority schemes on the target manually.

        1. aftermig.png
          aftermig.png
          149 kB
        2. source.png
          source.png
          92 kB
        3. target.png
          target.png
          66 kB

            Assignee:
            Unassigned
            Reporter:
            Fábio W. [Atlassian]
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: