Skip to main content
Azure DevOps integration enables automatic work item creation for failures that Bugzy triages as product bugs. When tests fail and Bugzy determines the failure is a genuine product issue, it creates a work item in your Azure DevOps project with full reproduction details.

​
What Azure DevOps enables

  • Automatic work item creation — Triaged product failures are filed as work items without manual intervention
  • Duplicate detection — Bugzy checks existing work items before creating new ones to avoid duplicates
  • Rich bug reports — Work items include reproduction steps, error details, screenshots, and environment info

​
Setup

1

Navigate to connections

Go to Dashboard > Projects > [Your Project] > Connections.
2

Connect Azure DevOps

Click Connect Azure DevOps. This opens the OAuth flow managed by Nango.
3

Authorize access

Select your Azure DevOps organization and authorize the requested permissions.
4

Configure project mapping

After connecting, map your Bugzy project to the target Azure DevOps project where work items should be created.

​
How work item creation works

The work item creation flow follows the same pattern as Jira bug filing:
  1. Test execution — Bugzy runs tests and collects results
  2. Triage — Bugzy analyzes failures, categorizing each as: product bug, test issue, or environment problem
  3. Duplicate check — For product bugs, the agent searches existing work items to avoid duplicates
  4. Create work item — If no duplicate exists, a work item is created with structured details
  5. Notify team — If Slack/Teams is connected, the team is notified about the new work item

​
Work item contents

Each filed work item includes:
FieldContent
TitleConcise description of the failure
DescriptionDetailed reproduction steps
Error detailsStack traces, error messages, assertion failures
ScreenshotsCaptured during test execution
EnvironmentBrowser, OS, app version, test URL
Tagsbugzy-automated, test case ID

​
Troubleshooting

Work items not being created — Verify the Azure DevOps connection is active and the project mapping is configured. Check that the connected user has permission to create work items in the target project. Duplicate work items being filed — The agent uses title and error signature matching for duplicate detection. If you see duplicates, ensure the project field mapping is correct. “Forbidden” errors — The OAuth token may lack required permissions. Disconnect and reconnect Azure DevOps from the project connections page to re-authorize.