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

      Problem Definition

      During a Scoped Migration, if there is a project that has issue links and it is not part of the scoped Migration, the post-migration report should throw an error stating that the issue links will not be created.

      Currently, it just shows a warning that the "Issue link may not work unless the related project is migrated to destination"

      Suggested Resolution

      The Migration logs should throw an error that the issue link will not be created since the related project is not in the scoped migration.

      The Post Migration report should mention which issue links failed to create

      Workaround

      We need to manually compare the requiresattention.csv file from the post-migration report to find which links are not created.

      In Google sheet count the number of matches between column B (warning from the log) and column D( Projects in migration scope), so if you got “2“ in the result - the link should be recreated successfully, but if - “1“ - this means that only of the project from migration scope was in warning, so you will need to recreate such link manually

            [MIG-2003] An error should be thrown for issue links not created

            There are no comments yet on this issue.

              Unassigned Unassigned
              b731d3f9dc26 Rakesh Ranjan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: