Azure DevOps
Deliver bug reports as Azure Boards work items — Microsoft sign-in or PAT.
SnagRelay creates work items on Azure Boards (not Repos). You can connect in two ways.
Connecting — two options
From the Integration tab, choose Azure DevOps. You’ll see a choice screen:
1. Microsoft sign-in
Sign in with a work or school Microsoft account (Entra ID / Azure AD). Best when your organization uses Azure AD and OAuth is allowed.
2. Personal Access Token (PAT)
Enter your organization name and a PAT. Use this when:
- You sign in with a personal Microsoft account (Entra OAuth for Azure DevOps often doesn’t work for those accounts), or
- OAuth isn’t available in your environment
Create a PAT in Azure DevOps under User settings → Personal access tokens with at least:
- Work Items — Read & write
- Project and Team — Read
After connecting
- Choose your organization
- Choose the project
- Optionally set:
- Work item type — Automatic (recommended) or a specific type
- Default area
- Default sprint
SnagRelay picks the right defect type from the project’s process:
| Process | Typical work item | Severity field |
|---|---|---|
| Agile / Scrum / CMMI | Bug | Yes |
| Basic | Issue (no Bug type) | No |
What gets synced
Team members (assignees), areas, sprints/iterations, and process capabilities used for form fields and defaults.
What gets created
A work item in the selected project (Bug or Issue, depending on process), with title, description, screenshot attachment, and any form fields you enabled (severity, parent, area, sprint, tags, assignee).
Widget form fields (Azure)
On Form Fields you can expose Azure-specific options such as Severity, parent work item (e.g. User Story / Product Backlog Item), Area, Sprint, and Tags — availability depends on what the connected project supports.
Reconnecting
Use Reconnect (Microsoft sign-in) or Reconnect with token (PAT) if access is revoked or expired. See Integration Disconnected.