How to Exlude a work-item external links for repository located outside of target organization and project.

[GeorgeB-RIB]

I am migrating project_A from dev.azure.com/org-1/project_A to dev.azure.com/org-2/project_A.
dev.azure.com/org-1/project_A contains external links in its work-items to commits in dev.azure.com/org-1/project_B/_git/repo_wiget in the form of commit references.
The problem being that the project_B does not exist in the new organization (org-2) that I'm migrating to. This causes the migration to fail and shows the commit link as broken in the target project.
According to other posts I've read the migration tool does not support this scenario.

In version 16 config. Would it be possible to exclude the creation of external links in the target work-items by making use of the following?

"CommonTools": {
      "TfsChangeSetMappingTool": {
        "Enabled": false,
        "ChangeSetMappingFile": ""
      },
      "TfsGitRepositoryTool": {
        "Enabled": true,
        "Mappings": {}
      },
      "FieldMappingTool": {
        "Enabled": true,
        "FieldMaps": []
      },
      "TfsWorkItemEmbededLinkTool": {
        "Enabled": true
      },
      "TfsWorkItemLinkTool": {
        "Enabled": true,
        "FilterIfLinkCountMatches": true,
        "SaveAfterEachLinkIsAdded": false
      },
      "WorkItemMigrationConfig": {
        "Enabled": "True",
        "FilterWorkItemsThatHaveLinks": [
          {
            "LinkType": "ExternalLink",
            "Pattern": "https://external-organization.com/external-project*"
          }
        ]
      }
    }

[MrHinsh]

Do you know why they used "external link" rather than a normal commit like?

I think this would be a great addition to the tool!

---

Funding for us doing work on this tool is generally through 1) customer funding, or 2) donated free time.

Sponcer a Feature | Hire us directly