@DaveShaw it kind of works the other way around. If you create a field in a work item that is a drop-down list with the names of the commands, and they correspond to the names of the commands you created, you can modify the CommonProcessingConfig.xml file to reflect that you want to use this field as a Designator command.
- Add a new field called "MyCompany.Teams" with valid values "Team A | Team B | Team C"
- Create teams in your team project "Team A | Team B | Team C"
- Use "witadmin exportcommonprocessconfig" to get the file CommonProcessingConfig.xml.
- In the "CommonProjectConfiguration \ TypeFields \ TypeField" section, where type is a "team", change the refname to "MyCompany.Teams"
- Use "witadmin importcommonprocessconfig" to import the new CommonProcessingConfig.xml file.
- Test ... a lot ...
I created a blog post that suits you, although this is: Team Foundation Server 2012 Teams without a scope
Then you can use a custom field to store the command value for your ... command ...
WARNING: Command: Specifies the field used to map the backlog and taskbar pages to the command. This field should remain set by default, System.AreaPath.
These are the early days for this feature, so make sure you check that it works for you.
source share