Merging 2 projects into one : usage of KeepOutboundLinkTargetProcessor ?

[mikymikymike]

Hello all,

I need to merge 2 projects (from the same Organization, on the same server). This will be done by migrating the Workitems of Team Project A into Team Project B.
We are on a ADO on-premise instance, on ADO 2022.
Given that the Workitems in Project A have links to others Workitems in Project B (and even to other Workitems in a Project C), I want the relevant links to be recreated on the Workitems that will be created in B (from A).

I therefore turned to the Processor KeepOutboundLinkTargetProcessor, which seems suitable for this, but I am having difficulties using it.
I am getting an error indicating that I need to make a call to "Configure," but I cannot find a way to do this via the configuration file.

What are the best practices for using the Processor KeepOutboundLinkTargetProcessor?
Is this the most suitable option for my needs?

Configuration (for testing for only 2 workitems id) :

{
  "Serilog": {
    "MinimumLevel": "Information"
  },
  "MigrationTools": {
    "Version": "16.0",
    "Endpoints": {
	  "Source": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://<ado>/<org>/",
        "Project": "Test_MR",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "**********"
        }
      },
      "Target": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://<ado>/<org>",
        "Project": "Catalogue_Commun",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "*******"
        },
        "ReflectedWorkItemIdField": "Sogitec.CradleKey"
      },
    },
    "CommonTools": {
	},
    "Processors": [
		{
			"ProcessorType": "TfsWorkItemMigrationProcessor",
			"Enabled": true,
			"FilterWorkItemsThatAlreadyExistInTarget": "False",
			"UpdateCreatedBy": true,
			"UpdateCreatedDate": true,
			"SkipRevisionWithInvalidAreaPath": true,
			"SkipRevisionWithInvalidIterationPath": true,
			"WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.Id] IN (98592, 98545) ORDER BY [System.ChangedDate] desc",
		},
		{
			"ProcessorType": "KeepOutboundLinkTargetProcessorOptions",
			"Enabled": true,
			"WIQLQuery": "SELECT [System.Id] FROM WorkItems WHERE [System.TeamProject] = @TeamProject AND [System.Id] IN (98592, 98545) ORDER BY [System.ChangedDate] desc",
			"TargetLinksToKeepOrganization": "https://ssog-tfs/tfs/SandboxCollection/",
			"PrependCommand": "start",
			"SourceName": "Source",
			"TargetName": "Target",
		}
    ]
  }
}

Errors :

[12:08:14 INF] [16.1.0]  Migration Processor Complete TfsWorkItemMigrationProcessor
[12:08:14 INF] [16.1.0] TfsWorkItemMigrationProcessor completed in 00:00:00
[12:08:14 INF] [16.1.0] Processor: KeepOutboundLinkTargetProcessor
[12:08:14 INF] [16.1.0] Migration Context Start: KeepOutboundLinkTargetProcessor
[12:08:14 INF] [16.1.0] Processor::InternalExecute::Start
[12:08:14 INF] [16.1.0] Processor::EnsureConfigured
[12:08:14 FTL] [16.1.0] Error while running KeepOutboundLinkTargetProcessor
System.Exception: You must call Configure() first
   à MigrationTools.Clients.AzureDevops.Rest.Processors.KeepOutboundLinkTargetProcessor.EnsureConfigured() dans D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.AzureDevops.Rest\Processors\KeepOutboundLinkTargetProcessor.cs:ligne 51
   à MigrationTools.Clients.AzureDevops.Rest.Processors.KeepOutboundLinkTargetProcessor.InternalExecute() dans D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools.Clients.AzureDevops.Rest\Processors\KeepOutboundLinkTargetProcessor.cs:ligne 37
   à MigrationTools.Processors.Infrastructure.Processor.Execute() dans D:\a\azure-devops-migration-tools\azure-devops-migration-tools\src\MigrationTools\Processors\Infrastructure\Processor.cs:ligne 99
Error logged to Elmah.io!
!! Check for latest version - We fix issues constantly - If not, please create a discussion on https://github.com/nkdAgility/azure-devops-migration-tools/discussions so we can get this fixed !!
[12:08:14 INF] [16.1.0] KeepOutboundLinkTargetProcessor completed in 00:00:00
[12:08:14 ERR] [16.1.0] KeepOutboundLinkTargetProcessor The Processor MigrationEngine entered the failed state...stopping run
[12:08:14 INF] [16.1.0] Command ExecuteMigrationCommand completed in 00:00:48.6649644
[12:08:14 INF] [16.1.0] Check the logs for errors: C:\Users\mbocquet\Documents\NON_SAVE\utils\MigrationTools-16.1.0\logs\20250404120724

Thank you in advance for your help !

Regards,
Mickael

[MrHinsh]

I have never used the KeepOutboundLinkTargetProcessor....

But what you ask for I think is available in the TfsTeamProjectEndpoint configuration y enabling AllowCrossProjectLinking. Does that look like its what you are asking for?

[mikymikymike]

Hello,

Thank you for your answer.

I didn't know the "AllowCrossProjectLinking" option.
I tried it (on the 2 endpoints : source and target) but there is no effect on my problem.

In the TfsWorkItemMigrationProcessor, the links to other WI are still not migrated :

[11:47:23 INF] [16.1.0] Migrating link for 98545 of type RelatedLink
[11:47:23 WRN] [16.1.0]   [SKIP] Unable to migrate link where Link of type System.LinkTypes.Related-Forward where wiSourceL=98545, wiSourceR=98591, wiTargetL=106258, wiTargetR=98591 as target WI has not been migrated
[11:47:23 INF] [16.1.0] Migrating link for 98545 of type RelatedLink
[11:47:23 WRN] [16.1.0]   [SKIP] Unable to migrate link where Link of type System.LinkTypes.Hierarchy-Reverse where wiSourceL=98545, wiSourceR=96761, wiTargetL=106258, wiTargetR=96761 as target WI has not been migrated
[11:47:23 INF] [16.1.0] Migrating link for 98545 of type RelatedLink
[11:47:24 WRN] [16.1.0]   [SKIP] Unable to migrate link where Link of type System.LinkTypes.Related-Forward where wiSourceL=98545, wiSourceR=105952, wiTargetL=106258, wiTargetR=105952 as target WI has not been migrated
[11:47:24 INF] [16.1.0] Migrating link for 98545 of type RelatedLink
[11:47:24 WRN] [16.1.0]   [SKIP] Unable to migrate link where Link of type System.LinkTypes.Related-Forward where wiSourceL=98545, wiSourceR=96764, wiTargetL=106258, wiTargetR=96764 as target WI has not been migrated
[11:47:24 INF] [16.1.0] Migrating link for 98545 of type RelatedLink
[11:47:25 WRN] [16.1.0]   [SKIP] Unable to migrate link where Link of type Sogitec.Implements-Forward where wiSourceL=98545, wiSourceR=96774, wiTargetL=106258, wiTargetR=96774 as target WI has not been migrated
[11:47:25 INF] [16.1.0] Migrating link for 98545 of type RelatedLink
[11:47:25 WRN] [16.1.0]   [SKIP] Unable to migrate link where Link of type Microsoft.VSTS.Common.Affects-Forward where wiSourceL=98545, wiSourceR=96771, wiTargetL=106258, wiTargetR=96771 as target WI has not been migrated
[11:47:25 INF] [16.1.0] Migrating link for 98545 of type RelatedLink
[11:47:25 WRN] [16.1.0]   [SKIP] Unable to migrate link where Link of type Microsoft.VSTS.Common.TestedBy-Forward where wiSourceL=98545, wiSourceR=98578, wiTargetL=106258, wiTargetR=98578 as target WI has not been migrated

And the KeepOutboundLinkTargetProcessor is still not working ...

Mickael

[MrHinsh]

It shoud allow the maintinaing of links to other projects in the same collection.

[mikymikymike]

I tried, but it didn't work ... I may have missed something.
I am away of my office, I will check when I will be back