> For the complete documentation index, see [llms.txt](https://docs.bugsplat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugsplat.com/guides/integrating-with-tools/issue-trackers/azure-devops.md).

# Azure DevOps

Visual Studio Team Services (Azure DevOps) integration with BugSplat allows your team to create defects with a few clicks. Hyperlinks allow quick navigation from defects to crash reports and back. Defects created from BugSplat automatically include symbolic call stack information and other crash-specific data.

### Integrating Azure DevOps with BugSplat

1. Login to your BugSplat account.
2. Click the Gear icon (⚙️) in the top right of the page and navigate to the Database Settings page, and under **Database > Integrations >** **Defect Trackers**, select **Azure DevOps** from the options shown.
3. Enter your **Azure DevOps URL** and **Personal Access Token** into the appropriate fields.
4. Click **Update**.
5. If the connection is successful, you can select your desired project from the **Project** dropdown list.
6. Click **Update**.

### Creating an issue in Azure DevOps from a BugSplat crash report

1\. Create a new defect from the crash page or a [stack key](/education/bugsplat-terminology.md#stack-key) page by using the **Create Defect** button.

2\. Enter relevant details and click the **Submit** button to create the defect. You can also enter an existing **Defect ID** if you'd like to associate a crash or stack key with an existing issue from Azure DevOps.

3\. Click the link to view the new Azure DevOps defect created by BugSplat.

### Automated Defect Creation

Want to create issues in Azure DevOps automatically for each new crash or crash group? Check out the document on auto-creating defects in your third-party defect tracker tool [here](/guides/integrating-with-tools/issue-trackers/automatic-issue-creation.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bugsplat.com/guides/integrating-with-tools/issue-trackers/azure-devops.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.