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.
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.
Options
topSamples
topSample
There is no sample, but you can check the classic below for a general feel.Defaults
There are no defaults! Check the sample for options!Classic
{
"$type": "TfsWorkItemOverwriteAreasAsTagsProcessorOptions",
"Enabled": false,
"AreaIterationPath": null,
"SourceName": null,
"TargetName": null
}Metadata
topSchema
This is the JSON schema that defines the structure and validation rules for this configuration.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://devopsmigration.io/schema/schema.processors.tfsworkitemoverwriteareasastagsprocessor.json",
"title": "TfsWorkItemOverwriteAreasAsTagsProcessor",
"description": "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.",
"type": "object",
"properties": {
"AreaIterationPath": {
"description": "This is a required parameter. That define the root path of the iteration. To get the full path use `\\`",
"type": "string",
"default": "\\"
},
"Enabled": {
"description": "If set to `true` then the processor will run. Set to `false` and the processor will not run.",
"type": "boolean"
},
"Enrichers": {
"description": "List of Enrichers that can be used to add more features to this processor. Only works with Native Processors and not legacy Processors.",
"type": "array"
},
"RefName": {
"description": "`Refname` will be used in the future to allow for using named Options without the need to copy all of the options.",
"type": "string"
},
"SourceName": {
"description": "This is the `IEndpoint` that will be used as the source of the Migration. Can be null for a write only processor.",
"type": "string"
},
"TargetName": {
"description": "This is the `IEndpoint` that will be used as the Target of the Migration. Can be null for a read only processor.",
"type": "string"
}
},
"required": [
"enabled",
"sourceName",
"targetName"
]
}In this article
Project Information
Azure DevOps Marketplace
Maintainer
Created and maintained by Martin Hinshelwood of nkdagility.com
Getting Support
Community Support
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