IntegrationsAzure DevOps

Azure DevOps Integration

Integrate BugBrain with Azure DevOps to automatically create and manage work items from test failures.

Features

  • Auto-create work items from test failures (Bug type)
  • Board automation — Move to “Active” when BugBrain finds issue
  • Sprint planning — Add to current sprint automatically
  • Status sync — Update work item when test passes
  • Team routing — Assign to team based on failure area
  • Custom fields — BugBrain data attached to work items
  • Available on all plans

Setup

  1. Get Azure DevOps PAT

    • Azure DevOps → User Settings → Personal access tokens
    • Create token with Work Item Read & Write scope
    • Copy token
  2. Connect to BugBrain

    • Settings → Integrations → Azure DevOps
    • Paste PAT token
    • Select Organization, Project, Area Path
    • Choose Work Item Type (Bug, Task)
  3. Configure Rules

    • Set failure severity threshold
    • Configure team assignments

Work Item Creation

Created Work Items include:

  • Title: [BugBrain] Test Failure: {test_name}
  • Description: Failure details, expected behavior, fix suggestions
  • Area Path: From configuration
  • Iteration: Current sprint (optional)
  • Priority: Mapped from BugBrain severity
  • Assigned To: Team/person from routing rules

Severity → Priority Mapping

BugBrain SeverityAzure Priority
Critical1 (Highest)
High2
Medium3
Low4 (Lowest)

Board States

BugBrain automatically manages work item states:

  • New → Created by BugBrain
  • Active → When first detected
  • Resolved → When test passes again
  • Closed → After 7 days in Resolved state

Team Assignment

Route issues to teams by test area:

Authentication tests → @auth-team
Payment tests → @payments-team
API tests → @backend-team
UI tests → @frontend-team

Configure routing rules in Integration settings.

Sprint Integration

Add to current sprint automatically:

  • Always — Add all created work items to current sprint
  • Critical only — Only add critical failures to sprint
  • Never — Leave in backlog for manual planning

Custom Fields

BugBrain adds custom fields to work items:

  • BugBrain Execution ID — Link to execution report
  • Test Plan — Which test plan found the issue
  • Failure Category — Type of failure (selector_changed, timeout, etc.)
  • Confidence Score — AI analysis confidence (0-100%)

Deduplication

  • 24-hour window — Prevent duplicate work items
  • Match criteria — Same test + same failure type
  • Action — Updates existing item, adds comment

Example: Azure Pipeline Integration

In azure-pipelines.yml:

- script: |
    curl -X POST https://api.bugbrain.tech/webhooks/ci \
      -H "X-Bugbrain-Secret: $(BugBrainSecret)" \
      -d '{"branch": "$(Build.SourceBranch)"}'
  displayName: 'Run BugBrain Tests'

Troubleshooting

  • Work items not creating — Verify PAT token permissions
  • Wrong project selected — Check Organization/Project in Integrations
  • Assignment failing — Verify team/person name matches Azure DevOps
  • Sprint assignment missing — Enable “Add to current sprint” in settings
  • Custom fields not visible — Add custom field definitions to Azure DevOps project

Best Practices

  1. Use consistent Area Paths for easy work item organization
  2. Set up board automation for state transitions
  3. Review custom field values to track BugBrain-created items
  4. Link to code reviews when fixing issues