Is there a way to filter the NodeStructuresMigrationConfig about azure-devops-migration-tools HOT 5 CLOSED

Could be anything really. In my particular case I’m mostly only ever interested in one sub-path, as most of our projects are organized the same way — as an example: CCO CCO\ATC CCO\MTM CCO\PLA etc. each of ATC, MTM and PLA are teams/projects controlled by a department “CCO” — this facilitates planning across teams in a department and seems to work fairly well for us, but on occasion a project is moved to a different department, so I have to take everything under “ATC” for instance and move it to a new base project as so: CCO2\ATC So for a filter, I could see simply a single path, or perhaps a comma separated list if I need to do more than one: NodePaths: \CCO\ATC, \CCO\MTM A regex could work as well, but might be a bit overkill. For my case “Area” and “Iteration” paths are generally the same at the top two levels (so they would both be “CCO\ATC” for example and then differ after that level), for others however having two different filter criteria might be useful. The other potential alternative (and I seem to recall that this was how the really old MS supplied migration tool used to work) is simply to create node paths as required based on the ticket itself being migrated — rather than having a separate plugin for that purpose. Thanks James