Configure delegation of Azure DevOps issues to Incident Response

Create a webhook URL in Incident Response and configure it in Azure DevOps.

Before you begin

Role required: Responder, Manager, or Administrator

About this task

Note: While this integration with a third-party product is supported, the documentation here is based upon information provided by that third-party. More current information about the operation of that third-party’s system may be available from them directly.

Procedure

  1. Complete the steps in Configure Azure DevOps integration.
  2. Keep the Delegate Azure DevOps issues to Incident Response toggle switch on.
  3. Select the service that you want to associate with the integration. You have two options:
    • Azure DevOps assigns incidents to the service specified in the JSON payload.

      To associate the incident to the service that is defined in the payload, enter the JSON path where the service name can be found in the JSON path for the service field.

      For example, if the JSON path is $.resource.fields['Custom.Airservice'] and the Airservice field contains the value Demo, Incident Response will assign the incident to the Demo service.

      • If this service name already exists in Incident Response, the incident is assigned to it.
      • If the service name doesn't exist in Incident Response, then a new service is created and the incident is assigned to this service.
      • If you've crossed your subscription limit, then a new service is not created. The incident is assigned to the default service selected in the Default service in case service name is not found in the payload field.
      • If the JSON path specified for the service doesn't exist in the incident payload, then the incident is assigned to the default service selected in the Default service in case service name is not found in the payload field.
      • If the JSON path for the service exists, but there's no value given for it in the incident payload, then the incident is assigned to the default service selected in the Default service in case service name is not found in the payload field.
    • Azure DevOps assigns incidents to a default service in Incident Response.

      To associate the incident to the default service, leave the Service defined in payload? check box deselected and select a service in the Default service in case service name is not found in the payload field.

  4. Click Save and Generate webhook.
    This generates a webhook URL.
  5. Copy the webhook by clicking the copy icon (Copy icon.).
    You will need it when configuring Azure DevOps.

    Delegate to Azure DevOps.

    Note: If you don't want to send work items from Azure DevOps to Incident Response, turn the Delegate Azure DevOps issues to Incident Response toggle switch off.
  6. If you must change the default priority or state mappings between Azure DevOps and Incident Response, select the Field mapping tab and make the mapping changes.
    For the default mapping, see Priority and state mappings for Azure DevOps.
  7. Log in to your Azure DevOps instance.
  8. Select the project for which you want to delegate work items.
  9. Navigate to Project Settings > General > Service hooks.
    Service hook subscription.
  10. Click Create subscription.
  11. Select Web Hooks from the list and click Next.
    Create web hook.
  12. In the Trigger dialog box, select one of the following events and click Next.
    • Work item created
    • Work item updated
    • Work item deleted
    Note:

    Currently, only these three events are supported.

  13. In the Action dialog box, paste the webhook URL from Incident Response in the URL field.
    Paste webhook URL.

    Click Test to check the connection with Incident Response. If successful, a test incident is created in Incident Response.

    For detailed information about webhooks in Azure DevOps, see Webhooks.

  14. Click Finish.
    Note:

    Work items created before configuring the service hooks in Azure DevOps won't be synchronized with Lightstep Incident Response. Any updates to these work items in Azure DevOps will also be ignored.

What to do next

Delegate issues from Azure DevOps