New features added through feature enablement

Last Update: 4/5/2017

TFS 2017 | TFS 2015 | TFS 2013

NOTE

Feature availability: This topic applies only to team projects defined on an on-premises Team Foundation Server (TFS). Team projects hosted on Team Services update automatically with each service upgrade.

The Configure Features Wizard detects which features have and haven't been configured. Most new features include additions or changes to work item types (WITs), categories, or process configuration. New features are introduced with different updates to Team Foundation Server (TFS).

Feature Changes Update
New web form

Adds the WebLayout section within the FORM section of all work item type (WIT) definitions. This section supports the new work item tracking experience in the web portal. It includes the SystemControls section and the new LinksControlOptions for managing link relationships. To learn more, see WebLayout and Control elements and LinksControlOptions XML elements (Web form).

Note: When you upgrade an on-premises TFS to TFS 2017, the new web form is automatically available when you add team projects to a collection. (You don't have to run the Configure Feature Wizard.) For existing team projects, an admin is required to enable the new form. The reason the new form isn't automatically enabled for existing team projects is to prevent overwriting customizations made to existing work item types.

TFS 2017
Code Review Adds the Code Review Request and Code Review Response WITs and categories to the team project. These items support code review requests and responses from the My Work page in Team Explorer. My Work only appears when you have Visual Studio Premium or Visual Studio Ultimate installed.
To manually add them to a team project, see Add features manually.
TFS 2012
My Work Supports your ability to develop code and manage pending changes from the My Work page in Team Explorer. My Work only appears when you have Visual Studio Premium or Visual Studio Ultimate installed.
Adds the metastate-to-workflow state mapping in ProcessConfiguration for the Bug Category. If you need to manually update the bug workflow states and metastates, see Support bug update status using My Work.
TFS 2012
Feedback Adds the Feedback Request and Feedback Response WITs and categories to the team project. These items support feedback requests and responses.
To manually add them to a team project, see Add features manually.
TFS 2012
Planning Tools Adds or updates process configuration that supports using the Agile tools: product backlog, plan sprints, Kanban board, and more.
Agile tools depend on the WITs, categories, and process configuration definitions that are made. Definitions are interdependent.
See ProcessConfiguration XML element reference to learn more about defining the process configuration for your team project.
TFS 2012
Storyboarding Adds the Storyboards control and tab to requirement WIT for the team project--such as Product backlog item for Scrum, User Story for Agile, and Requirement for CMMI. The Storyboards control supports linking storyboards to the work item as well as launching the Storyboarding.
To manually add the tab to a WIT, see Add features manually.
TFS 2012
Portfolio Backlogs For first time updates, adds the Feature and Epic WIT and categories to the team project and modifies the process configuration to support portfolio backlogs. These features enable teams to activate the portfolio backlogs they work with to organize their backlogs.
Note: If you have previously updated your team project to add the Feature WIT and portfolio backlog, then you'll need to add the Epic WIT, category, and portfolio backlog manually. If your team project doesn't have the Epic WIT, you can add it manually.
To manually add Feature and Epics portfolio backlogs to a team project, see Add features manually.
TFS 2013, TFS 2015
Shared Parameters Adds the Shared Parameter WIT and category to the team project. You use Shared Parameter work items to run tests with different data.
To manually add them to a team project, see Add features manually.
TFS 2013.2
Test Plan and Test Suite Adds the Test Plan and Test Suite WITs and categories to the team project. These items support managing and customizing test plans and test suites similar to other WITs. See also Create a test plan.
To learn more about how this feature gets enabled, see Test Plan and Test Suite features.
TFS 2013.3
Bug Behavior Adds the required fields to the Bug WIT definition so that they can be treated like requirements or like tasks. Teams can configure this option as described in Show bugs on backlogs and boards feature.
If you need to manually add them to a team project, see Add features manually.
TFS 2015

Not all new features require feature enablement.

Test Plan and Test Suite features

The Test Plan and Test Suite WITs are added when you run the TFS Upgrade Wizard. They aren't enabled through the Configure Feature wizard. They support customization of test plans and test suites

The enhancements support:

  • Test plans and test suites are now work item types (WITs). You can add fields, change the workflow, and customize them like any other work item type.

  • The area path security model now contains permissions to Manage test suites. The Manage test plans permissions has been re-scoped to manage only test plans. Previously it covered permission management of both test plans and test suites.

  • The History field for test-related artifacts now provides a consolidated view of changes made to work item fields as well as changes to related artifacts such as test points and test configurations. A new field, the Test Suite Audit field, available in the test suite work item form, captures and displays these related artifact changes in the work item history.

The server upgrade automatically converts existing test plans and test suites to WITs and migrates test data and links. If it encounters a problem, a warning message appears in the server log. To learn more, see Update a team project manually to support test management.

To learn about changes introduced to Test Manager and the web portal, see Create a test plan.