Export (0) Print
Expand All

Update a customized process template to access new features

If your team project was created from a customized process template, you might need to make manual updates to access new features provided with Visual Studio Team Foundation Server 2013. You can add new features to a customized process template as described in this topic and then use the Configure Features wizard to update several existing projects. Or, if you’ve customized your team project since you created it, you can add features manually to an existing team project.

You can update your customized process template by adding the following work item types (WITs):

You will copy or add files from the folder of the latest version of process template that you download to the corresponding folder containing your customized process template definitions.

  1. If you’re updating a process template based on a version earlier than MSF 6.0 or Visual Studio Scrum 2.0, first apply the updates provided in the 2012 version of this topic.

    You can check the ProcessTemplate.xml file for version information.

  2. If you aren’t a member of the Project Collection Administrators group, get added. You’ll need these permissions to work with the process templates.

  3. Download the latest version of the process templates that is compatible with the one used to create your team project.

    Tip Tip

    To download or upload process templates, you must connect to TFS 2013 from either Visual Studio 2013 or Team Explorer 2013.

  4. Copy the Feature.xml file from the WorkItem Tracking/TypeDefinitions folder to the corresponding folder of your customized process template.

  5. Add the Feature Category to the Categories file located in the WorkItem Tracking folder.

    <CATEGORY name="Feature Category" refname="Microsoft.FeatureCategory">
        <DEFAULTWORKITEMTYPE name="Feature" />
      </CATEGORY>
    

    This supports using the Feature portfolio backlog.

  6. Open the WorkItems plug-in file located in the WorkItem Tracking folder.

    1. Add a task for uploading the Feature work item type to the <WORKITEMTYPES> section.

      <WORKITEMTYPE fileName="WorkItem Tracking\TypeDefinitions\Feature.xml" />
      
    2. Replace the two process configuration tasks within the PROCESSCONFIGURATION element…

      <PROCESSCONFIGURATION>
         <CommonConfiguration fileName="WorkItem Tracking\Process\CommonConfiguration.xml"/>
         <AgileConfiguration fileName="WorkItem Tracking\Process\AgileConfiguration.xml"/>
      </PROCESSCONFIGURATION>
      

      .. with the single element statement that references the ProcessConfiguration file.

      <PROCESSCONFIGURATION>
         <ProjectConfiguration fileName="WorkItem Tracking\Process\ProcessConfiguration.xml"/>
      </PROCESSCONFIGURATION>
      
  7. Copy the ProcessConfiguration file from the WorkItem Tracking/Process folder of the downloaded process template to your customized template folder in the same location.

    Incorporate any customizations that you made to the AgileConfiguration or CommonConfiguration files to ProcessConfiguration. For more information, see Process Configuration XML Reference.

  8. Delete the AgileConfiguration and CommonConfiguration files from the WorkItem Tracking/Process folder.

    Process configuration is now supported by the single file ProcessConfiguration.

  9. Replace the Backlog/Stories/Requirement Overview.rdl and Stories/Requirements Progress.rdl files in the Reports folder of your customized template folder with the files of the downloaded process template in the same location.

    These updates reflect changes required with the introduction of the Feature portfolio backlog work item type as described in this blog post: Update your Overview and Progress reports to support the Portfolio backlogs.

  10. Open the ProcessTemplate plug-in file located in the top folder.

    1. Update the name to reflect the version changes you’ve made. For example:

      <name>MyCompany Custom Scrum 2013 </name>
      
    2. Update the code snippet after the description element. Your choice of code snippet is based on the template category that you are updating:

      Category

      Version statement

      Agile

      <version type="ADCC42AB-9882-485E-A3ED-7678F01F66BC" major="7" minor="17"/>
      

      CMMI

      <version type="27450541-8E31-4150-9947-DC59F998FC01" major="7" minor="7"/>
      

      Scrum

      <version type="6B724908-EF14-45CF-84F8-768B5384DA45" major="3" minor="7"/>
      
  11. Replace the Process Guidance folder, located under Windows SharePoint Services folder, with the contents of the latest folder.

    These files provide forward links to the latest process guidance content.

  12. Upload the process template and verify your changes.

    Use the Configure Features wizard to update a team project that was created using the process template that you just updated.

Copy or add files from the folder of the latest version of process template that you download to the corresponding folder containing your customized process template definitions.

  1. If you haven’t upgraded TFS to TFS 2013.2, get the download and run the upgrade.

  2. If you aren’t a member of the Project Collection Administrators group, Get added. You’ll need these permissions to run the wizard and download process templates.

  3. Download the latest version of the process template that is compatible with the one used to create your team project.

    To download or upload process templates, you must connect to TFS 2013 from either Visual Studio 2013 or Team Explorer 2013.

  4. Copy the SharedParameter.xml file from the WorkItem Tracking/TypeDefinitions folder to the corresponding folder of your customized process template.

  5. Add the Shared Parameter Category to the Categories file located in the WorkItem Tracking folder.

    <CATEGORY name="Shared Parameter Category" refname="Microsoft. SharedParameterCategory">
        <DEFAULTWORKITEMTYPE name="Shared Parameter" />
      </CATEGORY>
    
  6. Add Shared Parameter to Hidden Types Categories.

    <CATEGORY name="Hidden Types Category" refname="Microsoft.HiddenCategory">
        <DEFAULTWORKITEMTYPE name="Code Review Request" />
        <WORKITEMTYPE name="Code Review Response" />
        <WORKITEMTYPE name="Feedback Request" />
        <WORKITEMTYPE name="Feedback Response" />
        <WORKITEMTYPE name="Shared Steps" />
        <WORKITEMTYPE name="Shared Parameter" />  </CATEGORY>
    
  7. Open the WorkItems plug-in file located in the WorkItem Tracking folder.

  8. Add a task for uploading the Shared Parameter WIT to the <WORKITEMTYPES> section.

    <WORKITEMTYPE fileName="WorkItem Tracking\TypeDefinitions\SharedParameter.xml" />
    
  9. Open the ProcessTemplate plug-in file located in the top folder.

    1. Update the name to reflect the version changes you’ve made. For example:

      <name>MyCompany Custom Scrum 2013.2  </name>
      
    2. Update the code snippet after the description element. Your choice of code snippet is based on the template category that you are updating:

      Category

      Version statement

      Agile

      <version type="ADCC42AB-9882-485E-A3ED-7678F01F66BC" major="7" minor="19"/>
      

      CMMI

      <version type="27450541-8E31-4150-9947-DC59F998FC01" major="7" minor="9"/>
      

      Scrum

      <version type="6B724908-EF14-45CF-84F8-768B5384DA45" major="3" minor="9"/>
      
  10. Upload the process template and verify your changes.

    Use the Configure Features wizard to update a team project that was created using the process template that you just updated.

When you upgrade your application-tier server to TFS 2013.3, the TFS Upgrade Wizard automatically updates your existing team projects to support the new work item tracking objects for test plans and test suites.

Changes are made to your team project but no changes are made to any existing customized process templates. You can manually update your customized process templates, however. Reasons you'd do this include supporting future TFS upgrades that require using the Configure Features Wizard, or if you plan to create team projects with your customized process template on your upgraded server. You need to manually add these objects to your customized process templates.

  1. If you haven’t upgraded your application-tier server to TFS 2013.3, get the download and run the upgrade.

  2. If you aren’t a member of the Project Collection Administrators group, Get added. You’ll need these permissions to download process templates.

  3. Download the latest version of the process template that is compatible with the one used to create your team project.

    To download or upload process templates, you must connect to TFS 2013 from either Visual Studio 2013 or Team Explorer 2013.

  4. Copy the TestPlan.xml and TestSuite.xml files from the WorkItem Tracking/TypeDefinitions folder to the corresponding folder of your customized process template.

  5. Add the Test Plan Category and Test Suite Category to the Categories file located in the WorkItem Tracking folder.

    <CATEGORY name="Test Plan Category" refname="Microsoft.TestPlanCategory">
        <DEFAULTWORKITEMTYPE name="Test Plan" />
      </CATEGORY>
      <CATEGORY name="Test Suite Category" refname="Microsoft.TestSuiteCategory">
        <DEFAULTWORKITEMTYPE name="Test Suite" />
      </CATEGORY>
    
  6. Add the Test Plan Category and Test Suite Categoryto Hidden Types Categories.

    <CATEGORY name="Hidden Types Category" refname="Microsoft.HiddenCategory">
        <DEFAULTWORKITEMTYPE name="Code Review Request" />
        <WORKITEMTYPE name="Code Review Response" />
        <WORKITEMTYPE name="Feedback Request" />
        <WORKITEMTYPE name="Feedback Response" />
        <WORKITEMTYPE name="Shared Steps" />
        <WORKITEMTYPE name="Shared Parameter" />
        <WORKITEMTYPE name="Test Plan" />
        <WORKITEMTYPE name="Test Suite" />
      </CATEGORY>
    
  7. Open the WorkItems plug-in file located in the WorkItem Tracking folder.

  8. Add a task for uploading the Test Plan and Test Suite WITs to the <WORKITEMTYPES> section.

    <WORKITEMTYPE fileName="WorkItem Tracking\TypeDefinitions\TestPlan.xml" />
    <WORKITEMTYPE fileName="WorkItem Tracking\TypeDefinitions\TestSuite.xml" />
    
  9. Open the ProcessTemplate plug-in file located in the top folder.

    1. Update the name to reflect the version changes you’ve made. For example:

      <name>MyCompany Custom Scrum 2013.3  </name>
      
    2. Update the code snippet after the description element. Your choice of code snippet is based on the template category that you are updating:

      Category

      Version statement

      Agile

      <version type="ADCC42AB-9882-485E-A3ED-7678F01F66BC" major="7" minor="20"/>
      

      CMMI

      <version type="27450541-8E31-4150-9947-DC59F998FC01" major="7" minor="10"/>
      

      Scrum

      <version type="6B724908-EF14-45CF-84F8-768B5384DA45" major="3" minor="10"/>
      
  10. Upload the process template.

    To verify your changes, you can create a test project.

A: The Configure Features wizard uses the version statement to determine which process template within a category is the latest version and automatically selects that version.

If the version statement is not present, the Configure Features wizard cannot select the process template for updating a team project. Also, if more than one process template has been uploaded to Team Foundation Server that specifies the same highest version number, then none of these process templates can be selected for updating a team project.

A: If you want to use your existing WIT Feature to support a portfolio backlog, then you can skip step 3 and complete the remaining steps. However, if you want to add a different named WIT for your portfolio backlog, then you’ll need to modify the categories and process configuration definition files prior to import to reflect the different naming. See Add a Portfolio Backlog.

A: You can add up to five portfolio backlogs. This includes the default backlog of Feature. You can add this to a custom process template or after your team project is updated. To get started, see Add a Portfolio Backlog.

A: To view and work with portfolio backlogs requires that each team member has Full access.

A: You can post a question or search for answers in one of these forums: Team Foundation Server - Work Item Tracking or Team Web Access.

Show:
© 2014 Microsoft