Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-17392 Next-Gen projects
  3. JSWCLOUD-18643

When migrating between next-gen and classic projects Epic links info is lost and instead conversion should automatically maintain this data link between project types

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Open (View Workflow)
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Problem Definition

      Presently, anytime you convert a project between Next-gen and classic (or vice versa) the epic relationship between the epic and the children issues is not kept. This is documented in https://confluence.atlassian.com/jirasoftwarecloud/migrate-from-an-next-gen-project-to-a-classic-project-957974933.html

      Epics: Jira moves your epics across if you map them to an epic issue type in your new project. But, you'll lose the relationship between your epics and their child issues. The child issues themselves will sill exist, but the links between them won't.

      Suggested Solution

      The process to convert between these projects should be able to maintain that relationship between epic and issues in that epic.

      Why this is important

      Data is lost when converting due to this missing ability.

      Workaround

      None

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              aheinzer Andy Heinzer
              Votes:
              7 Vote for this issue
              Watchers:
              12 Start watching this issue

                Dates

                Created:
                Updated: