Mapping of Areas not working as described in documentation

[TobiasIs]

My task is to move from "DevOps A" to a "DevOps B", Areas and Sub-Areas to already existing Areas and Sub-Areas. To do this, I used the documentation and and the solutions described here in GitHub to create a configuration for the workprocessor.

Unfortunately, it does not copy the WorkItems into the prepared Areas or Sub-Areas, but always wants to create the source Areas or source Sub-Areas in the target, to copy the WorkItems there. I have tried different settings for "NodeBasePaths" none has led to the desired effect.

These are the ones I have tried:
"NodeBasePaths": ["Source Area".]
"NodeBasePaths": null
"NodeBasePaths": []

As written, there has been no change in the behavior, regarding the Areas or Sub-Areas.

The goal is to copy the Areas as follows:

Project ABC\Clients\ -> Project BCD\Win Cl.
Project ABC\Clients\Client Extern\ -> Project BCD\Win Cl\Clients\CDM CE
Project ABC\Clients\Client Management Extern\ -> Project BCD\Win Cl\Clients\CDM CME
Project ABC\Clients\Software\ -> Project BCD\Win Cl\SW
Project ABC\Clients\Hardware\ -> Project BCD\Win Cl\HW\

Thank you very much for your input already.

My configuration file looks like this:

{
"ChangeSetMappingFile": null,
"Source": {
"$type": "TfsTeamProjectConfig",
"Collection": "https://dev.azure.com/DevOps A/",
"Project": "Procject ABC",
"ReflectedWorkItemIDFieldName": "Custom.ReflectedWorkItemId",
"AllowCrossProjectLinking": false,
"AuthenticationMode": "Prompt",
"PersonalAccessToken": "",
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
},
"Target": {
"$type": "TfsTeamProjectConfig",
"Collection": "https://dev.azure.com/DevOps B/",
"Project": "Project BCD",
"ReflectedWorkItemIDFieldName": "Custom.ReflectedWorkItemId",
"AllowCrossProjectLinking": false,
"AuthenticationMode": "Prompt",
"PersonalAccessToken": "",
"LanguageMaps": {
"AreaPath": "Area",
"IterationPath": "Iteration"
}
},
"GitRepoMapping": null,
"LogLevel": "Information",
"Processors": [
{
"$type": "WorkItemMigrationConfig",
"Enabled": true,
"ReplayRevisions": true,
"PrefixProjectToNodes": false,
"UpdateCreatedDate": true,
"UpdateCreatedBy": true,
"WIQLQueryBit": " AND [System.AreaPath] UNDER 'Project ABC\Clients\' AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan', 'Test Case')",
"WIQLOrderBit": " [System.ChangedDate] desc",
"LinkMigration": true,
"AttachmentMigration": true,
"AttachmentWorkingPath": "c:\temp\WorkItemAttachmentWorkingFolder\",
"FixHtmlAttachmentLinks": false,
"SkipToFinalRevisedWorkItemType": true,
"WorkItemCreateRetryLimit": 5,
"FilterWorkItemsThatAlreadyExistInTarget": false,
"PauseAfterEachWorkItem": false,
"AttachmentMaxSize": 480000000,
"AttachRevisionHistory": false,
"LinkMigrationSaveEachAsAdded": false,
"GenerateMigrationComment": false,
"NodeStructureEnricherEnabled": true,
"NodeBasePaths": ["Clients"],
"AreaMaps": {
"^Project ABC\\Clients\\": "Project BCD\Win Cl\",
"^Project ABC\\Clients\\Client Extern\\": "Project BCD\Win Cl\Clients\CDM CE\",
"^Project ABC\\Clients\\Client Management Extern\\": "Project BCD\Win Cl\Clients\CDM CME\",
"^Project ABC\\Clients\\Software\\": "Project BCD\Win Cl\SW\",
"^Project ABC\\Clients\\Hardware\\": "Project BCD\Win Cl\HW\"
},
"IterationMaps": {},
"WorkItemIDs": null,
"MaxRevisions": 0
}
],
],
"Version": "13.1",
"workaroundForQuerySOAPBugEnabled": false,
"WorkItemTypeDefinition": {
"sourceWorkItemTypeName": "targetWorkItemTypeName"
},
"Endpoints": {
"InMemoryWorkItemEndpoints": [
{
"Name": "Source",
"EndpointEnrichers": null
},
{
"Name": "Target",
"EndpointEnrichers": null
}
]
}
}

[MrHinsh]

@TobiasIs even with mappings there is no way to filter the area and iteration paths that are created in the target. It will always create all of the area and iteration paths from the Source in the target.

Currently, there is no filter based on the loaded items, but I agree that would be a good idea.

Could you be more specific on what from the documentation is not correct?

1. "NodeBasePaths": ["Clients"], will only migrate WorkItems that appear under that Area Path.

2. "AreaMaps": will map the area path in each work item to a new path.

Neither of these have any affect on the Areas & Iterations that are created at the start of the migration.

[TobiasIs]

Thanks for your feeedback. I was not aware, that it creates the area paths in the target even the AreaMaps is configured.

If I understood correctly, the WorkItems are redistributed based on the AreaMaps. This is not done in my configuration, all WorkItems in the target can be found in the "old" path (area) and not in the new path (area) as configured. Therefore I think I have a bug in my configuration, unfortunately I can't find it.

The configuration I posted is based on the documentation and I don't think it is wrong, I think I just expressed myself unfortunate in my post.

[MrHinsh]

Your mappings are not going to match! Check the special characters section!

"AreaMaps": {
"^Project ABC\\\\Clients": "Project BCD\Win Cl",
"^Project ABC\\\\Clients\\\\Client Extern": "Project BCD\Win Cl\Clients\CDM CE",
"^Project ABC\\\\Clients\\\\Client Management Extern": "Project BCD\Win Cl\Clients\CDM CME",
"^Project ABC\\\\Clients\\Software": "Project BCD\Win Cl\SW",
"^Project ABC\\\\Clients\\Hardware": "Project BCD\Win Cl\HW"
},

And there should be no training slash!