From da8f0934dd676cc64cd29ab9ae6173d2f15ab8bb Mon Sep 17 00:00:00 2001
From: "Martin Hinshelwood nkdAgility.com" <martin@nkdagility.com>
Date: Mon, 5 Feb 2024 16:37:35 +0000
Subject: [PATCH] Updated docs

---
 .../Processors/WorkItemMigrationContext-notes.md  |  9 +++++++--
 .../ProcessorEnrichers/TfsNodeStructure-notes.md  | 15 +++++++++++++++
 2 files changed, 22 insertions(+), 2 deletions(-)

diff --git a/docs/Reference/v1/Processors/WorkItemMigrationContext-notes.md b/docs/Reference/v1/Processors/WorkItemMigrationContext-notes.md
index af461fb76..ad010b404 100644
--- a/docs/Reference/v1/Processors/WorkItemMigrationContext-notes.md
+++ b/docs/Reference/v1/Processors/WorkItemMigrationContext-notes.md
@@ -1,4 +1,3 @@
-
 ## <a name="WIQLQueryBits"></a>WIQL Query Bits
 
 The Work Item queries are all built using Work Item [Query Language (WIQL)](https://docs.microsoft.com/en-us/azure/devops/boards/queries/wiql-syntax).
@@ -48,6 +47,8 @@ Moved to the ProcessorEnricher [TfsNodeStructure](../Reference/v2/ProcessorEnric
 
 Moved to the ProcessorEnricher [TfsNodeStructure](../Reference/v2/ProcessorEnrichers/TfsNodeStructure/)
 
+
+
 ## More Complex Team Migrations
 The above options allow you to bring over a sub-set of the WIs (using the `WIQLQueryBit`) and move their area or iteration path to a default location. However you may wish to do something more complex e.g. re-map the team structure. This can be done with addition of a `FieldMaps` block to configuration in addition to the `NodeBasePaths`.
 
@@ -73,4 +74,8 @@ A complete list of [FieldMaps](../Reference/v1/FieldMaps/index.md) are available
 
 ```
 
-> Note: This mappings could also be achieved with other forms of Field mapper e.g. `RegexFieldMapConfig`, but the value mapper as an example is easy to understand
\ No newline at end of file
+> Note: This mappings could also be achieved with other forms of Field mapper e.g. `RegexFieldMapConfig`, but the value mapper as an example is easy to understand
+
+# Removed Properties
+
+- PrefixProjectToNodes - This option was removed in favour of the Area and Iteration Maps on [TfsNodeStructure](../Reference/v2/ProcessorEnrichers/TfsNodeStructure/)
\ No newline at end of file
diff --git a/docs/Reference/v2/ProcessorEnrichers/TfsNodeStructure-notes.md b/docs/Reference/v2/ProcessorEnrichers/TfsNodeStructure-notes.md
index d445f930d..712f20ff0 100644
--- a/docs/Reference/v2/ProcessorEnrichers/TfsNodeStructure-notes.md
+++ b/docs/Reference/v2/ProcessorEnrichers/TfsNodeStructure-notes.md
@@ -185,6 +185,21 @@ _NOTE: You need `\\` to escape a `\` the pattern, and `\\` to escape a `\` in JS
 
 ![image](https://github.com/nkdAgility/azure-devops-migration-tools/assets/5205575/2cf50929-7ea9-4a71-beab-dd8ff3b5b2a8)
 
+### Example with PrefixProjectToNodes 
+
+This will prepend a bucket to the area and iteration paths. This is useful when you want to keep the original paths but also want to be able to identify them as being from the original project.
+
+```json
+
+```json
+"AreaMaps": {
+  "^OriginalProject(?:\\\\([^\\\\]+))?\\\\([^\\\\]+)$": "TargetProject\\BucketForIncommingAreas\$2",
+},
+"IterationMaps": {
+  "^OriginalProject(?:\\\\([^\\\\]+))?\\\\([^\\\\]+)$": "TargetProject\\BucketForIncommingInterations\$2",
+}
+```
+
 ### Example with AreaMaps and IterationMaps
 
 ```