Manage notifications for a team or group

Azure DevOps Services | Azure DevOps Server 2019 | TFS 2018 | TFS 2017

As changes occur to work items, code reviews, pull requests, source control files, and builds, your team or group can be notified via email. For example, when a high priority work item is assigned to your team's area path, an email can be sent to the team.

Note

The notifications user interface changed with TFS 2017 Update 1. If you are working on TFS 2017 or earlier version, change the content version selector for this article to TFS 2015.

Create a custom email subscription

A subscription lets you control what your team should be notified about and how the team receives those notifications.

Note

For on-premises Azure DevOps Server, you must configure an SMTP server in order for team members to see the Notifications option from their organization or user profile menu and to receive notifications.

  1. Open the Notifications page under team settings: https://dev.azure.com/{organization}/{project}/_admin/_notifications?view=contents

    Navigate to team notifications page

  2. Select New subscription. If you're not a team administrator, get added as one. You need to be a team, project, or project collection administrator to create team alerts.

    New subscription

  3. Select the type of activity you want your team to be notified of.

    Select event category and template

  4. Provide a description to help you identify the subscription later.

    Select event category and template

  5. Choose which team members should receive a notification:

    Select role

    You can choose one of the following delivery options:

    • Team members by role: only certain team members associated with the event are notified. For example, for work item changes, you might only want the current assignee of the work item to receive a notification.
    • Team preference: use the team's default delivery preference. Learn how to manage delivery settings below.
    • Custom email address: send an email to a specified email address.
    • All team members: send an individual email to each member of the team.

    For certain activities and when Team members by role is selected, you can choose to have the user that initiated the activity receive a notification. This is controlled by the Skip initiator checkbox. By default, this box is checked meaning the user that initiates the change is not notified about it.

  6. Choose whether you want to receive notifications about activity in all projects or only a specific project.

    Select scope

  7. Optionally configure additional filter criteria.

    Select scope

  8. Select Finish to save the new subscription.

  1. Open the Notifications page under team settings: https://dev.azure.com/{organization}/{project}/_admin/_notifications?view=contents

    Navigate to team notifications page

  2. Select New subscription. If you're not a team administrator, get added as one. You need to be a team, project, or project collection administrator to create team alerts.

    New subscription

  3. Select the type of activity you want your team to be notified of.

    Select event category and template

  4. Provide a description to help you identify the subscription later.

    Select event category and template

  5. Choose which team members should receive a notification:

    Select role

    You can choose one of the following delivery options:

    • Team members by role: only certain team members associated with the event are notified. For example, for work item changes, you might only want the current assignee of the work item to receive a notification.
    • Team preference: use the team's default delivery preference. Learn how to manage delivery settings below.
    • Custom email address: send an email to a specified email address.
    • All team members: send an individual email to each member of the team.

    For certain activities and when Team members by role is selected, you can choose to have the user that initiated the activity receive a notification. This is controlled by the Skip initiator checkbox. By default, this box is checked meaning the user that initiates the change is not notified about it.

  6. Choose whether you want to receive notifications about activity in all projects or only a specific project.

    Select scope

  7. Optionally configure additional filter criteria.

    Select scope

  8. Select Finish to save the new subscription.

  1. Open the Notifications page under team settings: https://dev.azure.com/{organization}/{project}/_admin/_notifications?view=contents

    Navigate to team notifications page

  2. Select New subscription. If you're not a team administrator, get added as one. You need to be a team, project, or project collection administrator to create team alerts.

    New subscription

  3. Select the type of activity you want your team to be notified of.

    Select event category and template

  4. Provide a description to help you identify the subscription later.

    Select event category and template

  5. Choose which team members should receive a notification:

    Select role

    You can choose one of the following delivery options:

    • Team members by role: only certain team members associated with the event are notified. For example, for work item changes, you might only want the current assignee of the work item to receive a notification.
    • Team preference: use the team's default delivery preference. Learn how to manage delivery settings below.
    • Custom email address: send an email to a specified email address.
    • All team members: send an individual email to each member of the team.

    For certain activities and when Team members by role is selected, you can choose to have the user that initiated the activity receive a notification. This is controlled by the Skip initiator checkbox. By default, this box is checked meaning the user that initiates the change is not notified about it.

  6. Choose whether you want to receive notifications about activity in all projects or only a specific project.

    Select scope

  7. Optionally configure additional filter criteria.

    Select scope

  8. Select Finish to save the new subscription.

Manage team delivery settings

Choose the default method for your team to receive notifications by updating the team delivery settings.

Note

For on-premises Azure DevOps Server, you must configure an SMTP server in order for team members to see the Notifications option from their organization or user profile menu and to receive notifications.

  1. Open the Notifications page under team settings: https://dev.azure.com/{organization}/{project}/_admin/_notifications?view=contents

    Navigate to team notifications page

  2. Choose Delivery settings:

    Delivery settings

  3. Choose which option best fits your team's needs:

    Delivery settings options

Your team delivery settings are updated for notifications.

Manage group delivery settings

Manage your group notifications by updating the group's Delivery settings.

  1. Sign in to your organization (https://dev.azure.com/{yourorganization}).

  2. Select gear icon Organization settings. Open Organization settings

  3. Select Global notifications > Subscribers, enter and find your group, and then select Delivery settings.

    Group notification settings

  4. Choose which option best fits your group's needs, and then select Save.

    Delivery settings options

Your group delivery settings are updated for notifications.

Set alerts for your team

  1. If you're not a team administrator, get added as one. You need to be a team, project, or project collection administrator to create team alerts.

  2. Open team alerts from Manage TFS Alerts.

    Open team alerts

  3. Expand the team and open Select New Alert Template.

    Work Item Alerts link on the Alerts admin page

  4. Choose an alert type.

    Choose an alert type for the team

  5. Notice how the subscriber is set to the team context. Alerts are sent to each team member based on their preferred email address, which they set through their profile.

    Subscriber set to team context

    Tip

    For the team context, the alert query interprets the @Me variable as anyone who is a member of the team.

You can set filters for as many as 20 different alert types, specify the email addresses for yourself and other team members, and select the delivery format. Also, you can set team alerts to keep all team members notified of important changes.

Administer alerts for a project

To administer alerts for a project, you must be a member of the Project Collection Administrator or Team Foundation Administrator groups. To get added, see Add an administrator. If you're not a member of these groups, you won't see the options available for administering alerts.

As an administrator, you can view, create, edit, and delete alerts for team members and teams.

View alerts set for a project

  • From the web admin page for a project, open the Alerts tab and expand All alerts.

    Expand All Alerts

Find alerts set for a team member or team

  • Choose the name of the team member from the drop down list, or type the name in the search box.

    Choose the team member whose alerts you want to edit

    Alerts listed for selected team member

Create, edit, or delete an alert

  1. To create an alert for a team member, first find the alerts defined for that subscriber as described in the previous step. Then, create an alert in the same way that a team member creates alerts.

    Create an alert for a team member

    To create an alert for a team, first find the alerts assigned to that team, and then create an alert in the same way. The team should appear in the Subscriber field.

  2. To edit or delete an alert, open it from the short cut menu.

    Open or delete an alert for a team member