> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tekma.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Send a capture to Azure DevOps

> Connect an Azure DevOps project and create a work item with supported type, area, team, and field values.

Azure DevOps delivery creates a work item from a saved capture. A workspace owner configures one organization and project. Members use the configured project; owners can choose another accessible project in that organization for one work item. The organization is fixed by the connection and cannot be changed in the send form.

## Requirements and connection

Use **Continue to Azure DevOps** with Microsoft Entra OAuth when enabled, or **Use a token instead** with a PAT that can read work-item metadata and create work items. Setup requires a workspace owner. The connection form asks for **Organization**, **Project**, and optional **Work item type**. Use the organization name rather than a full organization URL.

1. Open **Settings → Integrations** and choose **Connect** next to Azure DevOps.
2. Choose **Continue to Azure DevOps**, or choose **Use a token instead** and enter the PAT.
3. Enter **Organization**, **Project**, and optional **Work item type** (for example `Bug`). Choose **Connect Azure DevOps**.
4. Confirm **Connected**. Use **Manage** to change the project or default type while keeping an existing credential.

## Send a work item

1. Open a saved capture and choose **Send to app → Azure DevOps**.
2. Wait for **Loading preview…** and review project, work-item type, title, description and private capture link.
3. Choose **Project**, **Work item type**, **Team**, **Area**, **Priority**, and **Assignee** when those resources are exposed. Add supported fields using the field reference name and its provider-defined value. Supported field values include string/plain text or escaped HTML, integer, double, boolean, ISO date-time, and allowed-value fields. Team selection supplies the team's configured area path; it is not a free-text Team field.
4. Use **Edit visible fields** where available, add context, and choose **Send to Azure DevOps**.
5. Open the returned work item and verify type, area, team-derived path, and selected fields. If the result is unconfirmed, inspect Azure DevOps before retrying.

| Field             | Supported values                                                                              |
| ----------------- | --------------------------------------------------------------------------------------------- |
| Organization      | Fixed configured organization                                                                 |
| Project/type      | Accessible project and exposed work-item type                                                 |
| Team/area         | Team member and explicit configured area; team maps to area-path settings                     |
| Priority/assignee | Values and members exposed by the selected project/team                                       |
| Other fields      | String/plain text/escaped HTML, integer, double, boolean, ISO date-time, allowed-value fields |

The item contains report text, sanitized source URL, capture kind and a private Tekma link. It does not upload media, screenshots, comments, or raw DevTools evidence. Before creation Tekma performs a non-persisting Azure validation request, then creates the item and reads it back; a validation failure does not create an item.

## Troubleshooting

If projects or work-item types are empty, verify organization, PAT scope/OAuth permissions, and project membership. If an area is missing, add it to the connection's explicit area choices or choose a supported area. Required fields of unsupported types block delivery; choose a value exposed by Tekma or a work-item type whose rules can be satisfied. A timeout after the validation step may still follow creation, so search Azure DevOps before sending again.