End of Support and End of Life
The Microsoft Azure DevOps (VSTS) integration is no longer supported, and cannot be configured by new users. The integration will reach its end of life in October 2023.
- Manually or automatically create VSTS work items from a PagerDuty incident.
- Notify on-call responders for critical VSTS work items.
- Dashboard widgets display PagerDuty incident information and on-call schedules.
- Admins, Global Admins and Account Owners can configure the integration.
- Users must have sufficient permissions to install extensions, create personal access tokens (PATs), and edit organization settings (Extensions).
- Responders, Managers, Admins, Global Admins and Account Owners can create work items from PagerDuty incidents.
- Users must have sufficient permissions to manage work items.
- Create VSTS work items within PagerDuty via webhooks.
- Create PagerDuty incidents in VSTS using a PagerDuty REST API key.
- View PagerDuty incidents within VSTS without logging in to PagerDuty.
- Navigate to PagerDuty in the Visual Studio Marketplace and click Get it free.
- With your account selected, click Install.
- Click Proceed to organization.
- Next, you will generate a personal access token (PAT) — go to User settings Personal access tokens.
- Click New Token and create a token with the following configuration:
- Name: Enter a name for your personal access token, for example, “PagerDuty Extension”.
- Expiration: Select Custom defined and enter a date one year in the future.
- Scopes: Select Custom defined and click Show all scopes.
- Extension Data: Read & write
- Extensions: Read & manage
- Project and Team: Read & write
- Security: Manage
- Work Items: Read, write, & manage
- Click Create.
- In the success pane, copy your PAT to the clipboard; you will use it in the next section.
- Note: Please store your PAT in a safe place. For security’s sake, Microsoft does not store it, and you will not be able to see it again after closing the success message.
- In the web app, go to Integrations Extensions.
- With the tab Service Extensions selected, click New Extension.
- From the dropdown, select Azure DevOps (Formerly Microsoft VSTS), and in the modal window click Open.
- Enter your personal authorization token (PAT) and click Save token.
- Enter the appropriate information for the following fields:
- Select PagerDuty Services
- Select a VSTS Account
- Select a Work Item
- Sync Work Items
- Click Add to VSTS.
- To complete the integration, go to Organization settings PagerDuty Configuration.
- In the field Default email for incident creation, enter an email address associated with a valid PagerDuty user. In the field API Key, enter a PagerDuty REST API key.
- Click Save.
If you selected Automatically in step 12 above, all PagerDuty incidents on the selected service(s) will open work items in the associated VSTS project. If you selected Manually, you can turn a PagerDuty incident into a VSTS work item in the PagerDuty web app.
- In PagerDuty, navigate to an incident that triggered on a service with the VSTS extension configured. Select More Create Work Item.
- Refresh the page to view the direct link to the work item in VSTS.
- In VSTS, go to Boards Work items.
- Click New Work Item and select Epic, Issue or Task, depending on the context.
- Enter a Title for your work item and click Save.
- Refresh the page.
- In the section PagerDuty Incident, search for or select a service and click Create Incident.
Note: If you receive an error message related to the requester’s email address or API key, please validate the information you entered in the final configuration steps.
- In VSTS, go to your project select Dashboards click Add a widget or select a dashboard and click Edit.
- In the Add Widget pane, search for
pagerdutyand select PagerDuty Incidents or PagerDuty OnCall.
- Click Add.
- Reorganize the widgets’ layout, if needed, and click Done Editing.
Updated about 1 month ago