GitRepositoryEnricher: Target Repo not found, TfsGitRepositoryTool

[kannnababu]

Title: TfsGitRepositoryTool
Path: _reference/reference.tools.tfsgitrepositorytool.md

I discovered that the links to Commits are broken and displaying the following error after the migration was completed
GitRepositoryEnricher: Target Repo not found. Cannot map https://*****/***Collection/Test/_git/ to ???

Upon analysing the problem, I have determined that it is looking for the repository in the target project that is mentioned in the configuration; if it is not found, an error is being thrown.

In my situation, the repository is located in a different project than what is specified in the configuration file. Therefore, the repository name must be searched in a different project. However, it can't do that.

Could you please check if this tool allows you to locate the repository in a separate project for work item commits?

Below is configuration i used,

"Processors": [
{
"ProcessorType": "TfsWorkItemMigrationProcessor",
"Enabled": true,
"UpdateCreatedDate": true,
"UpdateCreatedBy": true,
"WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @teamproject AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan','Code Review Request','Shared Steps','Shared Parameter','Feedback Request','Code Review Response') AND [System.ID] IN (251655) ORDER BY [System.ChangedDate] desc",
"FixHtmlAttachmentLinks": true,
"WorkItemCreateRetryLimit": 5,
"FilterWorkItemsThatAlreadyExistInTarget": false,
"PauseAfterEachWorkItem": false,
"AttachRevisionHistory": false,
"GenerateMigrationComment": true,
"WorkItemIDs": null,
"MaxGracefulFailures": 0,
"SkipRevisionWithInvalidIterationPath": false,
"SkipRevisionWithInvalidAreaPath": false,
"Enrichers": null,
"SourceName": "Source",
"TargetName": "Target",
"RefName": null
}
],
"CommonTools": {
"TfsGitRepositoryTool": {
"Enabled": "True",
"Mappings": [{"Test.ProjectName" : "Test3.ProjectName"}]
},
"StringManipulatorTool": {
"Enabled": "True",
"Manipulators": [
{
"$type": "RegexStringManipulator",
"Description": "Remove invalid characters from the end of the string",
"Enabled": "False",
"Pattern": "[^( -~)\n\r\t]+",
"Replacement": ""
}
],
"MaxStringLength": "1000000"
},
"FieldMappingTool": {
"Enabled": true,
"FieldMaps": [
]
}
}

[MrHinsh]

No, the tool does not support having linked repos in a separate project from the one work items are migrated to.

[GeorgeB-RIB]

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]

This is off topic from the context of this post. please create a new topic.