-
|
I'm moving a project from one devops org to another. All works fine, except one thing. If in the source project there is a comment in which there is a ticket mentioned let's say with id 111 (devops automatically adds a link to it of type 'Related to'), then when migrated in the target project I have 2 links - one is correct the originally mentioned/linked ticket that now has a new id and the also another ticket from totally different project in the target organization with the id 111. Also in the comment it is not updated, shows id 111 (that is a different ticket in the target org) and a different name. Any suggestions how to deal with this? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Before you migrate the Git Repository into its new location in Azure DevOps you should turn off the automatic linking. This will prevent incorrect links when importing. After the migration, you can turn it back on for future commits.
|
Beta Was this translation helpful? Give feedback.
Before you migrate the Git Repository into its new location in Azure DevOps you should turn off the automatic linking. This will prevent incorrect links when importing.
After the migration, you can turn it back on for future commits.