Additional configuration options post update
Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013
This topic applies only to projects hosted on an on-premises Team Foundation Server (TFS). Projects defined on Azure DevOps Services update automatically with each service upgrade.
After you update your project with the Configure Features wizard, you have access to the latest features. However, you may need to make some additional configurations or customizations to support your work tracking needs. Also, you have access to some features based on the source control setting selected when your project was created.
Adds the Code Review Request and Code Review Response work item types (WITs). With them, you can request a code review and track code review responses.
Required: Configure an SMTP server for TFS. |
Required: Visual Studio (any version). Availability: Only supported when your project uses Team Foundation version control for source control.
Adds support for automatic update of bug status when using My Work. Use to automate some activities when developing code and managing pending changes.
||Required: Visual Studio (any version). Availability: Only supported when your project uses Team Foundation version control for source control.|
|Feedback||You can request feedback from your stakeholders and capture their comments on your working software. Reviewer feedback--in the form of videos, screenshots, type-written comments, and ratings--is captured into work items that you can review and use to create a bug or suggest a new backlog item.||
Required: Provide Advanced access to users who'll request feedback.
Required: Configure an SMTP server for TFS.
Required: Grant stakeholders permission.
These tools provide access to product and sprint backlogs, the Kanban board and task boards, and the ability to add teams.
Required: To work with sprint backlogs and boards, you must activate the sprints for each team.
Additional options that you can configure:
For additional customization options, see Customize work tracking objects.
With this feature, you can storyboard your ideas using the Storyboarding add-in to PowerPoint.
Required: Office PowerPoint 2007 or later
Required: Visual Studio Community (get your free download) or other Visual Studio version installed.
|Portfolio Backlogs||With Portfolio Backlogs enabled, you can use the Feature and Epic portfolio backlogs to organize your backlog by grouping related items into a hierarchical structure.
Most of your team will be able to view and create Epics and Features once you've enabled the Portfolio Backlogs feature. However, you may need to enable one or more of these backlogs for a team as described in Organize your backlogs.
All stakeholders and contributors to your project can view and add items to a portfolio backlog. However, to reorder, reparent, and exercise other portfolio backlog features, you need to have Advanced access.
Other resources you may find useful to manage your teams and backlogs:
|Shared Parameters||This feature adds the Shared Parameters work item type (WIT). With it you can repeat a test with different data.||No additional configurations or customizations required.|
|Test Plan and Test Suite||
This feature adds the Test Plan and Test Suite WITs, and converts existing test plans and test suites to work items. With this feature enabled, you can now customize these WITs like other work items, and create queries to find test plans and test suites.
To fully manage web-based test plans, you need to have Advanced access.
You can customize the test plan and test suite WITs in the same way you can customize other WITs. See these topics to learn more:
|Bug Behavior||This feature allows teams to choose whether to track bugs like requirements or like tasks.||To get started, each team must choose their preference as described in Show bugs on backlogs and boards feature.|
If you are the server administrator for TFS and don't actually contribute to a team, then you may want to remove yourself as a member, and add a project lead as the team administrator. (When you ran the Configure Features wizard, the system automatically added your user account as a team administrator for the project.)
If you have updated a project based on v5.0 of MSF for Agile, do the manual updates described in Update the Workflow for Agile Team Projects.
Test case management and custom workflow states
If you add or change the workflow states for the test plan or test suite type definitions, and you work from a Test Manager client provided with Visual Studio 2013.2 or earlier versions, you must also update the process configuration for the project as well. Otherwise, you'll encounter an Application detected an unexpected fault error when you connect to your project.
To resolve this error, see Import and export process configuration [witadmin].
Recommended updates to projects created from TFS 2012 process templates
There are no additional required customizations to make after updating from TFS 2012 to TFS 2015. However, there are some recommended updates to make to the workflow of specific WITs.
The updates bring your project up to date with the workflow settings that are defined in the latest versions of the default process templates.
You might want to update the workflow of specific WITs to support missing transitions, additional reasons, and field assignments. Making this update revises the workflow for the following WITs to the latest version of their process template workflow:
- Scrum 2.0 to Scrum 2013: Product Backlog Item and Bug
- Agile 6.0 to Agile 2013: User Story
- CMMI 6.0 to CMMI 2013: Requirement
If you haven't customized your work item types or process configuration, you can update the items quickly by using witadmin. Just download the latest version of the process template that is compatible with the one used to create your project and then import the updated WITs.
Recommended updates to projects created from TFS 2010 process templates
If you've updated a project that was created with an MSF v 5.0 Agile process template, then you'll also want to manually update the user story and task workflow assignments.
If you don't update the workflow, then the task board provides only two states, Active and Closed. This prevents you and your team from distinguishing between tasks that are in progress from those that haven't been started.