Work Items Migration - Area & Iterations maps #2600
Chandu001729
started this conversation in
General
Replies: 2 comments
-
@MrHinsh requesting your help to achieve this process |
Beta Was this translation helpful? Give feedback.
0 replies
-
It looks from your config that you have not followed the instructions on https://nkdagility.com/learn/azure-devops-migration-tools/Reference/Tools/TfsNodeStructureTool/ for configuring the node mappings. Note that mappings need double escaped:
Update: I have fixed the link in the message, and you can find the TfsNodeStructureTool listed in the left navigation on the site. |
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
-
I have Source and Destination projects in different orgs and have different Area and Iteration paths as below and i have my configuration as updated below but facing the error as:
I am trying to the migration as below
I have two ADO projects in a same org, but few of the Backlog items are already migrated to destination project, now we have a requirement of migrating all the existing items which are in below states "Closed, Removed, Done, Released & Design" and the Area and Iteration maps need to be same as Destination it should not overwrite with source things and It should ignore if the work item is already present in the destination.
[07:57:11 INF] [16.0.9] Replay all revisions of 3184 work items?
[07:57:11 INF] [16.0.9] Validating::Check all Target Work Items have the RefectedWorkItemId field
[07:57:11 INF] [16.0.9] Validating::Check that all work item types needed in the Target exist or are mapped
[07:57:11 INF] [16.0.9] Validating::Check that all Area & Iteration paths from Source have a valid mapping on Target
[07:57:11 WRN] [16.0.9] NodeStructureEnricher.NodePathNotAnchoredException(Levvia\ART 03\Audit Workflow\Integrations\Integration With PortfolioPM, Area)
[07:57:15 WRN] [16.0.9] NodeStructureEnricher.NodePathNotAnchoredException(Levvia\Levvia Train 03, Iteration)
[07:57:19 WRN] [16.0.9] !! There are MISSING Area or Iteration Paths
[07:57:19 WRN] [16.0.9] NOTE: It is NOT possible to migrate a work item if the Area or Iteration path does not exist on the target project. This is because the work item will be created with the same Area and Iteration path as the source work item with the project name swapped. The work item will not be created if the path does not exist. The only way to resolve this is to follow the instructions:
[07:57:19 WRN] [16.0.9] !! There are 2 Nodes (Area or Iteration) found in the history of the Source that are missing from the Target! These MUST be added or mapped before we can continue using the instructions on https://nkdagility.com/learn/azure-devops-migration-tools//Reference/v2/ProcessorEnrichers/TfsNodeStructureTool/#iteration-maps-and-area-maps
[07:57:19 WRN] [16.0.9] MISSING Area: sourcePath=Levvia\ART 03\Audit Workflow\Integrations\Integration With PortfolioPM, targetPath=null, anchored=False, IDs=4823086,4823094,4824438,4824439,4824523
[07:57:19 WRN] [16.0.9] MISSING Iteration: sourcePath=Levvia\Levvia Train 03, targetPath=null, anchored=False, IDs=4823086,4823094,4824438,4824439,4824523
[07:57:19 ERR] [16.0.9] Missing Iterations in Target preventing progress, check log for list. To continue you MUST configure IterationMaps or AreaMaps that matches the missing paths..
Source Iteration & Area Maps


Destination Iteration & Area Maps


Configuration File
Configuration.json
Beta Was this translation helpful? Give feedback.
All reactions