Tfs WorkItem Overwrite Areas As Tags Processor

A common issue with older TFS/Azure DevOps instances is the proliferation of Area Paths. With the use of Area Path for Teams and the addition of the Node Name column option these extensive tag hierarchies should instad be moved to tags.

Last updated: June 27, 2025 | Edit this page | Discuss this page

A common issue with older TFS/Azure DevOps instances is the proliferation of Area Paths. With the use of Area Path for Teams and the addition of the Node Name column option these extensive tag hierarchies should instad be moved to tags.

top

Options

ParameterTypeDescriptionDefault Value
AreaIterationPathStringThis is a required parameter. That define the root path of the iteration. To get the full path use \\
EnabledBooleanIf set to true then the processor will run. Set to false and the processor will not run.missing XML code comments
SourceNameStringThis is the IEndpoint that will be used as the source of the Migration. Can be null for a write only processor.missing XML code comments
TargetNameStringThis is the IEndpoint that will be used as the Target of the Migration. Can be null for a read only processor.missing XML code comments
top

Samples

top

Sample

Sample

There is no sample, but you can check the classic below for a general feel.
top

Defaults

Defaults

There are no defaults! Check the sample for options!
top

Classic

Classic

{
  "$type": "TfsWorkItemOverwriteAreasAsTagsProcessorOptions",
  "Enabled": false,
  "AreaIterationPath": null,
  "SourceName": null,
  "TargetName": null
}
top

Metadata

Project Information
Azure DevOps Marketplace
YouTube Channel
Maintainer

Created and maintained by Martin Hinshelwood of nkdagility.com

Getting Support
Community Support
Questions & Discussions

The first place to look for usage, configuration, and general help.

Commercial Support

We provide training, ad-hoc support, and full service migrations through our professional services.

Azure DevOps Migration Services
Documentation