Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-20753

Moving Epics from a team-managed project to a company-managed project lose their Epic Name

    XMLWordPrintable

Details

    Description

      Issue Summary

      When trying to migrate Epics from next-gen project to a Classic project, you are forced to enter a value for 'Epic Name' in the Bulk edit screen. This gives all Epics that name once they are moved to the Classic project.

      Steps to Reproduce

      1. Create some epics in a next-gen project
      2. Use the Bulk Edit feature in Issue Navigator
      3. Move the issues to a classic project
      4. Check the 'retain' checkbox next to each of the fields for the Classic epic
      5. When you submit this form, you are told the field for the Epic Name is required and you must submit a value
      6. Enter a value
      7. All Epics have that same value applied

      Expected Results

      The Epic Name is retained when moving from Classic to Next-gen

      Actual Results

      All the Epics have the same Name once migrated.

      Workaround

      None

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              npellow Nick
              Votes:
              3 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated: