Set team defaults
VSTS | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013
Each team has access to a number of Agile tools as described in About teams and Agile tools. Each tool references the team's default area path(s). Several tools reference the team's default and active iteration paths or sprints. Most teams choose one area path and several iteration paths to support their work tracking activities. However, to support other scenarios, it's possible for teams to choose several area paths to appear on their backlogs and boards.
Backlog iteration versus default iteration
Teams can set a default iteration different from the backlog iteration. The backlog iteration determines which items appear on the team's backlogs and boards. And, the default iteration determines what value is assigned to work items created from the team context.
All work items that you create from your team context are automatically assigned both the team's default area path and default iteration path.
For TFS 2015 and earlier versions, the default iteration is the same as the backlog iteration. The one value selected both filters items that appear on the team's backlogs and boards, and is assigned to work items created from the team context.
Open team settings
You set team defaults from team settings. If you're not a team administrator, get added as one. Only team or project administrators can change team settings.
From a web browser, open the web portal administrative context for your team.
Choose Previous navigation when you see a top-level blue bar. Choose New navigation if you see a vertical sidebar or if you enabled the New Navigation preview feature. The vertical sidebar, along with other navigational features, is enabled when the New Navigation preview feature has been enabled for the signed-in user or the VSTS organization. To learn how to use the web portal effectively, see Navigation Basics.
For on-premises TFS users, choose Previous Navigation for guidance.
Set team default area path(s)
All work items assigned to the area paths selected for a team appear on the backlogs and boards for that team. You can select one or more area paths and optionally include their sub-area paths. Choose to include sub-area paths when you want to support rollup views of work performed across several teams or areas.
All work items assigned to the area paths selected for a team appear on the backlogs and boards for that team. You can select a single area path, and optionally include their sub-area paths. Choose to include sub-area paths when you want to support rollup views of work performed across several teams or areas.
The default area path determines the default area path assigned to work items that are created from the team context.
Work items that appear on more then one team's Kanban board can yield query results that don't meet your expectations. Because each team can customize the Kanban board columns and swimlanes, the values assigned to work items which appear on different boards may not be the same. The primary work around for this issue is to maintain single ownership of work items by team area path.
Open the Work>Areas admin page for the team context.
Here, we navigate to the Web team.
Choose the area path(s) to be active for each team.
In this instance, we choose to activate all three sub-area paths for the project. This allows the management team to track progress across all three teams.
When you've finished, refresh the product backlog page for the team, and you'll see those work items assigned to the team. Add Area Path to the columns shown to see the assignments made to work items.
Open the Areas admin page for the team context.
Here, we navigate to the Web team. The checked box indicates the area paths selected for the team. To exclude sub-areas, select the option from the area path context menu.
Refresh the product backlog page for the team, and you'll see only those work items assigned to the Fabrikam Fiber\Web area path.
Select team sprints and default iteration path
You define sprints for the project and then select them to be active for each team. You assign the default iteration to use when creating new work items.