Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-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
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features 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:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: