From dd96a2d167558704c53b54f88a66786d17e4442b Mon Sep 17 00:00:00 2001 From: "Martin Hinshelwood nkdAgility.com" Date: Mon, 4 Mar 2024 17:50:23 +0000 Subject: [PATCH] Added PrefixProjectToNodes to docs --- .../ProcessorEnrichers/TfsNodeStructure-notes.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/Reference/v2/ProcessorEnrichers/TfsNodeStructure-notes.md b/docs/Reference/v2/ProcessorEnrichers/TfsNodeStructure-notes.md index 871848ab0..7d743c140 100644 --- a/docs/Reference/v2/ProcessorEnrichers/TfsNodeStructure-notes.md +++ b/docs/Reference/v2/ProcessorEnrichers/TfsNodeStructure-notes.md @@ -109,6 +109,20 @@ in the replacement string. `TargetProject\NewArea\ValidArea\` but `OriginalProject\DescopeThis` would not be modified by this rule. +### PrefixProjectToNodes + +The `PrefixProjectToNodes` was an option that was used to prepend the source project name to the target set of nodes. This was super valuable when the target Project already has nodes and you dont want to merge them all together. This is now replaced by the `AreaMaps` and `IterationMaps` options. + +``` +"IterationMaps": { + "^SourceServer\\\\(.*)" , "TargetServer\\SourceServer\\$1", +}, +"AreaMaps": { + "^SourceServer\\\\(.*)" , "TargetServer\\SourceServer\\$1", +} +``` + + ### More Complex Regex 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 and the migration will stop just after it outputs a list of the missing nodes.