TfsWorkItemOverwriteAreasAsTagsProcessor
Ref
Less than 1 minute to read
2024-09-10 16:11:58 +0000
draft
This page is in draft and may include errors or omissions. Please check the discussions for any pending updates and changes to the content or to suggest your own changes.
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
Parameter name | Type | Description | Default Value |
AreaIterationPath | String | This is a required parameter. That define the root path of the iteration. To get the full path use `\` | \ |
Enabled | Boolean | If set to `true` then the processor will run. Set to `false` and the processor will not run. | missng XML code comments |
Enrichers | List | List of Enrichers that can be used to add more features to this processor. Only works with Native Processors and not legacy Processors. | missng XML code comments |
RefName | String | `Refname` will be used in the future to allow for using named Options without the need to copy all of the options. | missng XML code comments |
SourceName | String | missng XML code comments | missng XML code comments |
TargetName | String | missng XML code comments | missng XML code comments |
Examples
defaults
1
2
There are no defaults! Check the sample for options!
sample
1
2
There is no sample, but you can check the classic below for a general feel.
classic
1
2
3
4
5
6
7
8
9
10
{
"$type": "TfsWorkItemOverwriteAreasAsTagsProcessorOptions",
"Enabled": false,
"AreaIterationPath": null,
"Enrichers": null,
"SourceName": null,
"TargetName": null,
"RefName": null
}