-
We are migrating from ADO to ADO (different Orgs). Target Project: "CompanyUno Migration Test" -- Source Project: "CompanyUno". CompanyUno had two projects: CompanyUno and CompanyUno Asset Management We are having an error: Path \CompanyUno Migration Test Asset Management\Iteration is not anchored in the target project, it cannot be created For the life of me I cannot figure out what we are missing. We had a similar issue with an Area Path we were able to resolve, but this time we are stuck. Im wondering if its related to a previous bug with spaces in the project name? It looks like its just not parsing in the names correctly in the path :/ here is what we have in the config: { Adding from log: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
I was able to get past the error by changing the mapping to this: "CommonEnrichersConfig": [ is there anyone who can explain why this worked compared to what I had in the original? It looks like Iteration and Area are just hidden values that ADO uses, but im not sure how do it without the * or if that is the correct way |
Beta Was this translation helpful? Give feedback.
There are clear examples on https://nkdagility.com/learn/azure-devops-migration-tools/Reference/v2/ProcessorEnrichers/TfsNodeStructure/
Issues:
^CompanyUno Asset Management
) would only match the exact name. It would not match any sub-items. This is a regular expression and you can use https://regex101.com/ to test your mappings.A solution from the documentation linked:
This would do t…