Skip to main content
The Azure DevOps integration lets Bugzy use Azure Boards and Azure Test Plans as your team’s QA system of record. One project connection supplies the Azure DevOps organization URL and personal access token (PAT) for both capabilities.

​
What Azure DevOps enables

  • Automatic work item creation — Triaged product failures are filed as work items after duplicate detection
  • Test Plans management — Discover and manage plans and nested static suites
  • Test Case management — Create and update manual Test Cases, steps, and suite membership
  • Test execution records — Resolve test points, create runs, record per-test outcomes, and complete runs
  • Durable Azure identity — Preserve Azure IDs and links from discovery through reporting
Azure remains the source of truth. Bugzy does not create a permanent local copy or bulk synchronization layer.

​
Setup

1

Create a personal access token

In Azure DevOps, create a PAT with Work Items: Read & write and Test Management: Read & write access for the target organization. Limit its organization and lifetime according to your team’s security policy.
2

Navigate to connections

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

Connect Azure DevOps

Click Connect Azure DevOps, then enter the organization URL (for example, https://dev.azure.com/your-org) and PAT in the secure connection form.
4

Confirm project access

Ensure the PAT’s user can read and write work items and Test Plans artifacts in the target Azure DevOps project.
Nango stores the connection credentials securely. Bugzy projects the organization URL and PAT into isolated agent runs; the agent never prints or persists the PAT.

​
Test Plans workflow

Bugzy follows Azure’s artifact hierarchy and preserves the returned identity at every step:
  1. Discover or create a test plan
  2. Discover or create nested static suites
  3. Discover or create manual Test Case work items with structured steps
  4. Add Test Cases to suites and resolve the generated test points
  5. Create a point-based test run
  6. Record or update each test result
  7. Complete and read back the run
Bugzy checks for exact matches before creating artifacts and stops when discovery is ambiguous. It does not retry an uncertain create blindly.

​
Supported boundaries

The integration supports plans, suite hierarchies, manual Test Cases, suite membership, test points, runs, and per-test outcomes. It does not delete Azure artifacts, upload binary attachments, store per-step execution outcomes, or automatically reconcile Playwright titles with Azure Test Case titles.

​
How work item creation works

For failures triaged as product bugs, Bugzy searches existing work items before filing a new one. New work items can include reproduction steps, error details, environment information, and links to test evidence. If Slack or Microsoft Teams is connected, Bugzy can notify the team after filing.

​
Troubleshooting

No projects or artifacts are returned — Verify the organization URL and confirm that the PAT’s user can access the target project. “Forbidden” or Test Management permission errors — Create or update the PAT with Test Management: Read & write and Work Items: Read & write, then reconnect Azure DevOps from the project connections page. A Test Case is not available in a suite — Test Case creation and suite membership are separate operations. Confirm the Test Case ID was added to the intended plan and suite, then list test points. A run already contains results — Point-based runs can create result records automatically. Bugzy lists results and updates their returned IDs instead of adding duplicates.