Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-11972

For a TMP that has been rekeyed doing a C2C migration migrate its board’s filter with the original key

XMLWordPrintable

      Issue Summary

      When doing a C2C migration with a TMP that has been re-keyed, the board filter will have a JQL using the original project key. This can be a problem for the Timeline of this project because no issues will appear since it’s pointing to the old project key. This is only a problem when the original key of the source site is already associated with an existing project on the target site.

      Steps to Reproduce

      1. Create a project with a key ‘ABC’ on the source site and create some issues.
      2. Change the project key to another key, ‘DEF’
      3. On the target site, create a project with the key ‘ABC’
      4. Migrate the source project to the target site

      Expected Results

      The Timeline should show all the issues from the ‘DEF’ project.

      Actual Results

      The Timeline is not showing any issues.

      Workaround

      Contact Migration Support through our portal.

            [CLOUD-11972] For a TMP that has been rekeyed doing a C2C migration migrate its board’s filter with the original key

            Bruno Souza added a comment -

            https://getsupport.atlassian.com/browse/PCS-342935

            This is also happening to users who changed the key for TMP, as the filter will be pointing to the old project key in the filter.

            Bruno Souza added a comment - https://getsupport.atlassian.com/browse/PCS-342935 This is also happening to users who changed the key for TMP, as the filter will be pointing to the old project key in the filter.

              Unassigned Unassigned
              361a3ab41fd2 Felipe Furtado
              Affected customers:
              5 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated: