AreaPath Mapping not working as expected #1482
Unanswered
joshmurari
asked this question in
Q&A
Replies: 1 comment
-
The mapps for the area and iteration paths are already upted to the target when the Area Mapper is run.. try this instead: {
"$type": "WorkItemMigrationConfig",
"Enabled": true,
"ReplayRevisions": true,
"PrefixProjectToNodes": false,
"UpdateCreatedDate": true,
"UpdateCreatedBy": true,
"WIQLQueryBit": "AND [System.WorkItemType] NOT IN ('Test Suite', 'Test Plan')",
"WIQLOrderBit": "[System.ChangedDate] desc",
"LinkMigration": true,
"AttachmentMigration": true,
"AttachmentWorkingPath": "c:\\temp\\WorkItemAttachmentWorkingFolder\\",
"FixHtmlAttachmentLinks": false,
"SkipToFinalRevisedWorkItemType": false,
"WorkItemCreateRetryLimit": 5,
"FilterWorkItemsThatAlreadyExistInTarget": false,
"PauseAfterEachWorkItem": false,
"AttachmentMaxSize": 480000000,
"AttachRevisionHistory": false,
"LinkMigrationSaveEachAsAdded": false,
"GenerateMigrationComment": true,
"WorkItemIDs": null,
"MaxRevisions": 0,
"NodeStructureEnricherEnabled": true,
"UseCommonNodeStructureEnricherConfig": false,
"StopMigrationOnMissingAreaIterationNodes": true,
"NodeBasePaths": [],
"AreaMaps": {
"^Migration-Target-1\\\\Contoso\\\\": "Migration-Target-1\\",
"^Migration-Target-1\\\\Contoso\\\\Data\\\\": "Migration-Target-1\\Data\\",
"^Migration-Target-1\\\\Contoso\\\\Data\\\\Data Core\\\\": "Migration-Target-1\\Data\\Data Engineering\\",
"^Migration-Target-1\\\\Contoso\\\\Data Reporting\\\\": "Migration-Target-1\\Data\\Data Reporting\\",
"^Migration-Target-1\\\\Contoso\\\\Finance\\\\": "Migration-Target-1\\Finance",
"^Migration-Target-1\\\\Contoso\\\\Finance\\\\DevOps\\\\": "Migration-Target-1\\Finance\\DevOps\\",
"^Migration-Target-1\\\\Contoso\\\\Finance\\\\Security\\\\": "Migration-Target-1\\Finance\\Security\\"
},
"IterationMaps": {
},
"MaxGracefulFailures": 0,
"SkipRevisionWithInvalidIterationPath": false,
"SkipRevisionWithInvalidAreaPath": false
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem Description
I was looking to get some guidance on how to properly structure my AreaMaps under the WorkItemMigrationConfig processor.
Here is the area path layout in my Source Project:
This is what I want the area path layout to look like in my Target Project:
What is being changed between the source and target:
Migration-Source-2/Contoso
area path is being deleted and all its sub area paths are now mapped to the root of the project..../Data/Data Core
area path is being renamed to.../Data/Data Engineering
.../Data Reporting
area path is being moved underneath.../Data
to look like.../Data/Data Reporting
This is what my processor config looks like:
But when I run this configuration my area paths end up looking like this instead!

It successfully moved all
.../Contoso/Data/...
and.../Contoso/Finance/...
area paths under the root of the project instead of being underneath.../Contoso/
. But the.../Contoso/
area path still exists in the Target project! How can I get rid of the.../Contoso/
Area path here?"^Migration-Source-2\\\\Contoso": "Migration-Target-1"
but this returns the error ofSystem.InvalidOperationException: This path is not a valid area or iteration path: Migration-Target-1
"^Migration-Source-2\\\\Contoso": "Migration-Target-1\\"
and this returns the error ofSystem.ArgumentException: TF200005: The following path is not correctly formatted: \Migration-Target-1.
This configuration also failed to rename
.../Data/Data Core
area path to.../Data/Data Engineering
. How do I get this rename to work?And lastly it also failed to move
.../Data Reporting
area path underneath.../Data
. How do I get this to work?Please let me know if I am missing something here and if you can help me format these AreaMaps correctly.
Beta Was this translation helpful? Give feedback.
All reactions