> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/integrations/azure-devops.md).
# Azure DevOps
Integrate Luciq with Azure DevOps to create work items from mobile bug reports automatically. Sync app monitoring with your DevOps pipeline.
{% hint style="info" %}
We only support one-way sync integration with Azure DevOps — changing statuses or assignees on Azure DevOps won't reflect on Luciq.
{% endhint %}
Forward your bug reports to your Azure DevOps workspace by following these simple steps.
{% stepper %}
{% step %}
**Navigate to Integrations**
Open Luciq's Settings and go to the Integrations page. Click *Create* on the Azure DevOps integration.
{% endstep %}
{% step %}
**Fill integration form**
In the integration form, you'll need to provide:
* PAT Token
* Organization URL
{% endstep %}
{% step %}
**Create a PAT Token (Personal Access Token)**
To create a new PAT Token in Azure DevOps:
* Head over to Azure DevOps.
* Click on User Settings from the menu.
* Choose "Personal Access Token", or navigate to this URL:\
{% endstep %}
{% step %}
**Configure the token**
Click on New Token, ensuring the new token has either full access or read-and-write access to work items.
{% endstep %}
{% step %}
**Enter credentials in Luciq**
Fill in your PAT Token and Organization URL in the integration form.
{% endstep %}
{% step %}
**Test and create**
Test the connection and create your integration.
{% endstep %}
{% step %}
**Configure forwarding and rules**
From the final page you can:
* Choose automatic forwarding of all bug reports or forward manually.
* Set Rules & Alerts based on conditions before forwarding.
{% endstep %}
{% endstepper %}
---
# 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.luciq.ai/product-guides-and-integrations/integrations/azure-devops.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)