I’m a big proponent for having one giant team project for an entire enterprise. Then using Teams and Areas to subdivide the enterprise into manageable chunks. There are massive amounts of benefits (check out this post: http://nakedalm.com/one-team-project/). However, a customer of mine made a good point the other day. He said that by having one giant team project, the Assigned To field now contained everybody (over 2000 people). What he wanted to happen was that depending on the Area selected, the assigned to field should only display those team members. After some thought, I figured this could be accomplished by modifying the Assigned To field so that when the area field is something, the allowed values would be a certain group. So i modified the User Story WIT to something like this
Unfortunately, this didn’t work. When I tried to upload the the UserStory.xml file, I got this error:
TF212017: Work item tracking schema validation warning: TF26171: User/group ‘MyProjectTeamA’ is not found.
TF26204: The account you entered is not recognized. Contact your Team Foundation Server administrator to add your account.
No matter what combination I tried, it seemed like the schema validation did not like back slashes for the area path. To work around this, instead of the area path, I used the area id. So something like this:
This worked. To figure out the area id, I just created a query and included area id as one of the columns. Then, i just flipped the area to all the different areas and go the area id.