Configure Features for process templates based on v 4.2 process templates
I have seen customers facing issues while configuring the new features for process templates based on v4.2 after upgrading to TFS 2012. You would see the below screen with a message
You must perform few changes to your process template in order to configure the new features.
Below are the steps that we need to follow:
1. First we need to export the latest process template from TFS as parts of this will be used in subsequent steps. For TFS 2012, MSF for Agile Software Development 6.2 is the latest. For TFS 2013.x download MSF for Agile Software Development 2013.x
2. Using witadmin.exe, import the following work item type definitions from the downloaded process template into each of your team projects that needs to be upgraded.
Below is the syntax to import a work item type
witadmin importwitd /collection:CollectionURL [/p:Project] /f:FileName
Example:
witadmin importwitd /collection:”https://tfsservername:8080/tfs/DefaultCollection /p:TeamProjectName /f:filename
For filename, mention the name with full path like c:\document\Userstory.xml
Use the above syntax to import all the workitem types below:
a. UserStory
b. TestCase- This required slight modification to the following system field names to remove spaces that were added since 2008 but that still exist based on the 2008 template.
i. External Link Count --> ExternalLinkCount
ii. Related Link Count --> RelatedLinkCount
iii. HyperLink Count --> HyperLinkCount
iv. Attached File Count --> AttachedFilecount
v. Area ID --> AreaID
c. SharedStep- This required slight modification to the following system field names to remove spaces that were added since 2008 but that still exist based on the 2008 template
i. Iteration ID --> IterationID
ii. External Link count --> ExternalLinkCount
iii. Related Link Count --> RelatedLinkCount
iv. HyperLink Count --> HyperLinkCount
v. Attached File Count --> AttachedFilecount
vi. Area ID --> AreaID
d. Task - Required because there are necessary fields (StartWork, StopWork) missing in the 4.2 version
Note: Before importing Task.xml, I would strongly recommend you to download a copy from the existing team project using witadmin exportwitd. Use the syntax below:
witadmin exportwitd /collection:collectionurl [/p:Project] /f:FileName
For 2013.X Process templates, along with above Workitem types import SharedParameter as well.
NOTE: In 2013.3, you may not need to modify the TestCase and SharedStep Workitem types as specified above. You can try to import them directly.
3. Using witadmin.exe, import the following Linked Types - NOTE: This is a onetime operation for the Team Project Collection and does not need to be run for each Team Project.
These LinkTypes will be available under downloaded process template
Syntax:
witadmin importlinktype /collection:CollectionURL /f:FileName
a) TestedBy
b) SharedStep
c) SharedParameterLink (for TFS 2013 only)
4. Using witadmin.exe, import categories for each Team Project being upgraded.
a. We first had to comment out references to all new 6.2 / 2013.X WITs (e.g. Code Review Request/Response) since they do not yet exist. These will be updated during the Configure operation in Step #5.
Comment out the Workitem types below:
- Code Review Request
- Code Review Response
- Feedback Request
- Feedback Response
- Feature (for TFS 2013 only)
- SharedParameter (for TFS 2013 only)
Syntax to import categories:
witadmin importcategories /collection:CollectionURL /p:Project /f:FileName
Note: FileName will be categories.xml which will be under workitem tracking folder.
5. Run Configure from the Admin site for each Team Project
a) After performing the above steps for a given Team Project you then need to navigate to the Admin site for the project. You can do this by clicking Web Access for the Team Project from Team Explorer as shown.
b) Then click on the Administrative icon
in the upper right corner of the page.
c) From the Administrative page you should see an option similar to the following indicating that you have features for this Team Project that are not configured. Click the Configure Features link.
d) This should result in a window similar to the following indicating the process template to which that your Team Project will be upgraded to.
e) Click on the Configure button and the Team Project should be upgraded to the new process template.
All the above steps would work for Agile process templates. If you try to configure the features for CMMI process templates, then you would receive error message below:
[Error] TF400654: Unable to configure Planning Tools. The following element contains an error:
RequirementWorkItems. TF400517: The value of this element is set to: Microsoft.VSTS.Scheduling.Size. You must set the value to a field that exists in all of the work item types that are defined in RequirementWorkItems. The field does not exist in the following work item types: Requirement.
[Error] TF400654: Unable to configure Planning Tools. The following element contains an error:
TypeFields/TypeField[type='Order']. TF400517: The value of this element is set to:
Microsoft.VSTS.Common.StackRank. You must set the value to a field that exists in all of the work item types that are defined in RequirementWorkItems. The field does not exist in the following work item types: Requirement.
The above error points missing fields in “Requirement” work item type. If you don’t have any customizations in this work item type, you can import the “Requirement” work item type from “MSF for CMMI Process Improvement 6.2”
Content created by Chandra Sekhar Viswanadha
Content Reviewed by Romit Gulati
Comments
- Anonymous
August 18, 2015
The comment has been removed