Manage and configure team tools

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019

If you're a team administrator, you have the flexibility to tailor your backlogs and boards to align with your team's workflow. In case you require a new team, you can ask a Project Administrator group member to create one for you, which takes only a minute. Team administrators have the ability to set up and oversee all team tools.

Team administrators perform the following tasks for team tools:

Prerequisites

  • To perform any team configuration task, you must be a team administrator for the team to be modified, or be a member of the Project Administrators group. For more information, see Change project-level permissions.
  • To add a team, you must be a member of the Project Administrators group. For more information, see Add teams.

Open your team profile

Open your team profile to quickly access items defined for your team.

  1. Sign in to your organization (https://dev.azure.com/{yourorganization}), and then open your project.

  2. Select Project settings > Teams > your team name.

    Screenshot of sequence to open a team.

Add users to a team

Tools like capacity planning, team alerts, and dashboard widgets operate within the scope of a team. They automatically access the user information of team members to facilitate planning tasks or issue alerts.

To add users to a team, see Add users to a project or specific team.

Screenshot of Add button highlighted, to add team member.

All members of a team can favorite team artifacts and define work item templates. For more information, see:

If team members don't have access to all the features they want, make sure they have the permissions needed for those features.

Add an administrator

When you add a team to a project, a Project Administrator should add one or more team administrators.

Screenshot of Add button highlighted, to add an administrator.

Configure team areas and iterations

Many Agile tools rely on the team's configured area and iteration paths. For more information, see About teams and Agile tools.

After project administrators add the project's area and iteration paths using Set area paths and Set iteration paths, team administrators can choose the relevant area and iteration paths for their team. These settings influence a wide range of Agile tools that the team can access.

Screenshot of Iterations and areas highlighted.

Settings include making the following associations for each team:

  • Select team area paths
    Can select the default area path(s) associated with the team. These settings affect many Agile tools available to the team.
  • Select team iteration paths or sprints Can select the default area path(s) associated with the team. These settings affect many Agile tools available to the team.

For more information, see Define area paths and assign to a team and Define iteration paths and configure team iterations.

Configure team backlogs, boards, and general settings

As a team administrator, you have the flexibility to customize your team's workflow to suit your needs. One way to do so is by choosing which backlog levels are active for your team. For instance, a feature team might only want to display the product backlog, while a management team might prefer to show the feature and epic backlogs only. Also, you can choose how to treat bugs within your workflow, either as user stories and requirements or as tasks.

Another way to customize your team's workflow is by selecting non-working days for the team. By doing so, sprint planning and tracking tools can automatically take these days off into account when calculating capacity and sprint burndown.

Most of these team settings can be easily configured from the common configuration dialog, providing a convenient way to manage your team's workflow in one central location. You can also set team automation rules to update work items when child item states change.

Note

For more information, see Backlogs, boards, and plans. In case you're not seeing the desired work items on your backlog or board, see Set up your backlogs and boards to configure them according to your preferences.

  1. Check that you selected the correct project, and then choose Boards > Boards, and select the correct team from the team selector dropdown menu. For more information, see Use breadcrumbs and selectors to navigate and open artifacts. Screenshot of steps to open the kanban board.

  2. Choose Team settings to configure the board and set general team settings.

    Screenshot of gear icon selection for general board settings.

  3. Choose a tab under any of the sections—Cards, Board, Charts, and General—to configure the cards or boards, the cumulative flow chart, or other team settings. When you're done configuring the settings, select Save and close.

    Screenshot of team settings page.

  1. Check that you selected the right project, (2) choose Boards > Boards, and then (3) select the correct team from the team selector menu.

    Open Kanban board, versions Azure DevOps Server 2019 and on.

  2. Make sure that you select the team backlog or board that you want to configure using the team selector. To learn more, see Use breadcrumbs and selectors to navigate and open artifacts.

  3. Choose the product or portfolio backlog from the board-selection menu.

    Choose board level, vert nav

  4. Choose Team settings to configure the board and set general team settings.

    Open board settings for a team, vert nav

  5. Choose a tab under any of the sections—Cards, Board, Charts, and General—to configure the cards or boards, the cumulative flow chart, or other team settings.

    Common configuration dialog team settings

Team administrators have complete control over customizing their team's Kanban boards for both the product and portfolio backlogs. To set up a Kanban board, you can define the columns and work-in-progress (WIP) limits through the common configuration dialog. For more information, see Kanban overview and Kanban quickstart.

For detailed information on each configuration option, you can explore the following articles:



Configure sprint taskboards

Similar to Kanban boards, you can customize each sprint taskboard to support information-rich color-coded cards and columns. For more information, see Customize sprint taskboards.

Similar to Kanban boards, each sprint taskboard can be customized to support information-rich, color-coded cards. For more information, see Customize sprint taskboards.

Screenshot of taskboard selection.

Add and manage team dashboards

By default, all team members can add and edit team dashboards. In addition, team administrators can manage permissions for team dashboards. For more information, see Add and manage dashboards.

Screenshot of dashboard button surrounded by red square.

Update team name, description, and image

Team settings also include the team name, description, and team profile image. To add a team picture, select the image icon. The maximum file size is 2.5 MB and 2560 x 1024 px, and then we resize to 200 x 200.

Screenshot to Update team profile picture.

Team settings also include the team name, description, and team profile image. To add a team picture. Open the Team Profile and choose the picture icon. The maximum file size is 4 MB.

Manage notifications

Team administrators have the ability to add and edit alerts, allowing the team to receive email notifications as changes occur to work items, code reviews, source control files, and builds. Various alerts are pre-defined for each team. For more information, see Manage team alerts.

Screenshot of highlighted Notifications button.