Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-1559

moved_issue_key table data not migrated

XMLWordPrintable

    • 7
    • 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.

      Customers rely on the link redirections that automatically occur due to the data in the moved_issue_key table.  When they migrate, that data is no longer available on the destination site to the customer's workflows become broken. 

      I was able to gather a mapping to provide to the customer using the following query:

      select m.old_issue_key
           , concat(j.pkey, '-', j.issuenum) as new_issue_key
           from jiraissue j
        join moved_issue_key m on m.issue_id = j.id
       --where j.pkey = '%%'
       --where m.old_issue_key like '%%'  

      Workaround:

      None currently.  Will update when a workaround is available.

            Unassigned Unassigned
            d037086145b0 Rick Rehmann (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: