Partilhar via


Add features using a manual update process

Go here to open the Visual Studio 2015 version of this topic.

You can update team projects that were created in earlier versions of Team Foundation Server (TFS) to use new features added with the upgrade to TFS 2013. You should update team projects by using the Configure Features wizard, see Configure features after a TFS upgrade. However, if the wizard is unable to add a feature, you can add it manually.

You can add the following work item types (WITs):

If you’re updating from TFS 2010, first apply the updates provided in the 2012 version of this topic.

Updates required to use portfolio backlogs

Import files from the folder of the latest version of process template that you download and update the categories definition files.

  1. If you haven’t upgraded TFS to TFS 2013, do that now. See Upgrade Team Foundation Server.

  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. Run the Configure Features wizard to determine which features need to be configured. See Configure features after a TFS upgrade.

    Verify features can be configured

    If the wizard lists additional features to configure besides Portfolio Backlogs, then first apply the updates provided in the 2012 version of this topic.

  4. Download the latest version of the process templates 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.

  5. Open a Command Prompt window where either Visual Studio 2013 or Team Explorer 2013 is installed and enter:

    cd %programfiles(x86)%\Microsoft Visual Studio 12.0\Common7\IDE
    

    On a 32-bit edition of Windows, replace %programfiles(x86)% with %programfiles%.

  6. Add the Feature WIT. Specify the DirectoryPath to the WorkItem Tracking/TypeDefinitions folder that contains the process template that you downloaded.

    witadmin importwitd /collection:CollectionURL /p:"ProjectName" /f:"DirectoryPath\Feature.xml"
    

    The directory path must follow this structure: Drive:\TemplateFolder\WorkItem Tracking\TypeDefinitions.

    An example of CollectionURL is http://MyServer:8080/tfs/DefaultCollection.

  7. Update the categories to support using the Feature portfolio backlog.

    1. First, export the categories file.

      witadmin exportcategories /collection:CollectionURL /p:ProjectName /f:"DirectoryPath\categories.xml"
      
    2. Add the Feature Category.

      <CATEGORY name="Feature Category" refname="Microsoft.FeatureCategory">
          <DEFAULTWORKITEMTYPE name="Feature" />
        </CATEGORY>
      
    3. Then, import the categories file.

      witadmin importcategories /collection:CollectionURL /p:ProjectName /f:"DirectoryPath\categories.xml"
      
  8. Import the new process configuration file from the WorkItem Tracking/Process folder of the downloaded process template. Process configuration is now supported by the single file ProcessConfiguration.

    witadmin importprocessconfig /collection:CollectionURL /p:ProjectName /f:"DirectoryPath\ProcessConfiguration.xml"
    

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

  9. You can start using the portfolio backlog as described here.

Updates required to use Shared Parameters, requires TFS 2013.2 (Update 2)

Import one file from the folder of the latest version of process template that you download, and modify the categories definition file.

  1. If you haven’t upgraded TFS to TFS 2013.2, get the download. Upgrade Team Foundation Server.

  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. Run the Configure Features wizard to determine which features need to be configured. See Configure features after a TFS upgrade.

    Configure features for TFS 2013.2

  4. Download the latest version of the process templates that is compatible with the version 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.

  5. Open a Command Prompt window where either Visual Studio 2013 or Team Explorer 2013 is installed and enter:

    cd %programfiles(x86)%\Microsoft Visual Studio 12.0\Common7\IDE
    

    On a 32-bit edition of Windows, replace %programfiles(x86)% with %programfiles%.

  6. Add the Shared Parameter WIT. Specify the DirectoryPath to the WorkItem Tracking/TypeDefinitions folder that contains the process template that you downloaded.

    witadmin importwitd /collection:CollectionURL /p:"ProjectName" /f:"DirectoryPath\SharedParameter.xml"
    

    The directory path will follow this structure: Drive:\TemplateFolder\WorkItem Tracking\TypeDefinitions.

    An example of CollectionURL is http://MyServer:8080/tfs/DefaultCollection.

  7. Add the Shared Parameter Category to the categories definition.

    1. Export the categories file.

      witadmin exportcategories /collection:CollectionURL /p:ProjectName /f:"DirectoryPath\categories.xml"
      
    2. Add the Shared Parameter Category.

      <CATEGORY name="Shared Parameter Category" refname="Microsoft. SharedParameterCategory">
          <DEFAULTWORKITEMTYPE name="Shared Parameter" />
        </CATEGORY>
      
    3. 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>
      
    4. Import the categories file.

      witadmin importcategories /collection:CollectionURL /p:ProjectName /f:"DirectoryPath\categories.xml"
      
  8. Verify that you can add a shared parameter set or convert to shared parameters. See Repeat a test with different data.

Q & A

Q: What if I already have a WIT named Feature defined in my team project?

A: If you want to use your existing WIT Feature to support a portfolio backlog, then you can skip step 5 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 importing these files to reflect the different naming. See Add a Portfolio Backlog.

Q: What if I want to use more than one level of portfolio backlog?

A: You can add up to five portfolio backlogs. This includes the default backlog of Feature. To get started, see Add a Portfolio Backlog.

Q: I’ve added portfolio backlogs to my team project. Why can’t all team members view them?

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

Q: Where can I learn more about the definition files to modify?

A: See these topics for more information:

Q: Where can I go if I have more questions?

A: You can post a question or search for answers in the Team Foundation Server forum.