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

As a Classic user who has moved Epics, I would like the classic migration to follow moved Epic issue keys

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Answered
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      When issues are moved from one project to another, this does not change the issue link used for Classic-mode Epics. As it's possible for JIRA to determine the historical issue key, it would be helpful if Epic labels that do not match an in-use issue key be matched against the issue keys of previously moved issues.

      Attachments

        Activity

          People

            Unassigned Unassigned
            jgarcia John Garcia (Inactive)
            Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: