Final post for tonight and then I might have a little nap on the train.
On another recently created project utilising the custom Team field to scope Work Items to TFS teams rather than the Area Path I encountered another minor issue.
I created a Test Plan using Microsoft Test Manager and then clicked the Open in Web Access button
I received the following error in Team Web Access:
The test plan with id XX does not exist or it’s area path is not owned by the default project team. Include it in the default project team’s owned areas and try again.
The error is a little cryptic as I hadn’t even started adding area paths, much less locking them down. It was in fact, another symptom of using the custom Team field,
I hadn’t implemented the template customisation and so the Work Item definition was missing the following on the Team field:
<DEFAULT from="value" value="Unassigned" />
TFS 2013 Update 3 requires that you add your Team field to the new Test Plan Work item. You don’t have to expose the field on the UI but it must have a default value or you will hit issues in Team Web Access when accessing those Test Plans that do not have the field populated.
Easy to resolve –
- Run a query into Excel that brings back all the Test Plan Work Items
- Add the Team field to the list of columns
- Set the Team value for the Test Plans to Unassigned (or whatever you use)
- Use witadmin.exe or the Process Template Editor to update your Work Item definitions to have a default Team value
Time for a snooze.