Processors : WorkItemMigrationConfig try to take other project data from source and ends to FTL error

[Manish-Jain-Affirma]

Source Env. : Azure DevOps

• Organisation : OrganisationOne
  • Project : Project One
  • Project : Project One New

Target Env. : Azure DevOps

• Organisation : OrganisationOne-Target
  • Project : Project One

Here I'm trying to migrate Project One from Source Env. to Target Env. So, the respective Source, Target config. has below parameters.

• "Source"
  "Collection": "https://dev.azure.com/organisationone/", "Project": "Project One",
• "Target"
  "Collection": "https://dev.azure.com/organisationone-target/", "Project": "Project One",

When I'm executing it with Only one enabled WorkItemMigrationConfig Processor. It throws fatal error with

[10:16:06 WRN] NodeStructureEnricher.NodePathNotAnchoredException(Project One New\Iteration 1, Iteration)
[10:16:14 FTL] !! There are 1 IterationPaths found in the history of the Source that are missing from the Target. These MUST be added or mapped with a fieldMap before we can continue.
[10:16:14 WRN] MISSING Iteration:

As you can see on the WRN, it is checking in Project One New from source, which I'm not trying to fetch as per the "Source" config.
Note : configuration.json has "Version": "13.0"

[MrHinsh]

There is a work item in Project One that was originaly created in Project One New and then moved to Project One. Therefor in the history of that work item there is an invlaid Iteration Path that will need to be mapped.

The bit just after you image in the log has the answer to what that iteraion is.

https://nkdagility.com/learn/azure-devops-migration-tools/Reference/v1/Processors/WorkItemMigrationContext/

[tdebusscher]

I'm struggling with the exact same case, some PBI's were moved from one project to another and then I receive the error

MigrationTools.FieldMaps.NodePathNotAnchoredException: This path is not anchored in the source project name: Digicreate.Maintenance.Scrum

Can you explain a bit your solution more? Is it in the config file in the section 'IterationMaps' that I need to make some changes?

[MrHinsh]

Check out https://nkdagility.com/learn/azure-devops-migration-tools/Reference/v1/Processors/WorkItemMigrationContext/#iteration-maps-and-area-maps

[MrHinsh]

As per the documentation, you need to add Iteration Maps and Area Maps that adapt the old locations to new ones that are valid in the Target.

Before your migration starts it will validate that all of the Areas and Iterations from the Source work items revisions exist on the Target. Any that do not exist will be flagged in the logs and if you have "StopMigrationOnMissingAreaIterationNodes": true, set the migration will stop just after it outputs a list of the missing nodes.

Our algorithm that converts the Source nodes to Target nodes processes the mappings at that time. This means that any valid mapped nodes will never be caught by the This path is not anchored in the source project message as they are already altered to be valid.

We recently updated the logging for this part of the system to more easily debug both your mappings and to see what they system is doing with the nodes and their current state. You can set "LogLevel": "Debug" to see the details.

To add a mapping, you can follow the documentation with this being the simplest way:

"IterationMaps": {
  "WorkItemMovedFromProjectName\\\\Iteration 1": "TargetProject\\Sprint 1",
},
"AreaMaps": {
   "WorkItemMovedFromProjectName\\\\Team 2": "TargetProject\\ProductA\\Team 2",
}

Or you can use regular expressions to match the missing area or iteration paths:

"IterationMaps": {
  "^OriginalProject\\\\Path1(?=\\\\Sprint 2022)": "TargetProject\\AnotherPath\\NewTeam",
  "^OriginalProject\\\\Path1(?=\\\\Sprint 2020)": "TargetProject\\AnotherPath\\Archives\\Sprints 2020",
  "^OriginalProject\\\\Path2": "TargetProject\\YetAnotherPath\\Path2",
},
"AreaMaps": {
  "^OriginalProject\\\\(DescopeThis|DescopeThat)": "TargetProject\\Archive\\Descoped\\",
  "^OriginalProject\\\\(?!DescopeThis|DescopeThat)": "TargetProject\\NewArea\\",
}

If you want to use the matches in the replacement you can use the following:

"IterationMaps": {
  "^\\\\oldproject1(?:\\\\([^\\\\]+))?\\\\([^\\\\]+)$": "TargetProject\\Q1\$2",
}

If the olf iteration path was \oldproject1\Custom Reporting\Sprint 13, then this would result in a match for each Iteration node after the project node. You would then be able to reference any of the nodes using "$" and then the number of the match.

Regular expressions are much more difficult to build and debug so it is a good idea to use a regular expression tester to check that you are matching the right things and to build them in ChatGTP.

NOTE: You need \\ to escape a \ the pattern, and \\ to escape a \ in JSON. Therefor on the left of the match you need 4 \ to represent the \\ for the pattern and only 2 \ in the match