What You Can Do
Once connected, PlayerZero AI agents can:- Read work items - Access bugs, tasks, user stories, and their full history for debugging context
- Create and update work items - Generate work items from debug sessions with proper fields and relationships
- Add comments - Post discussion comments with investigation findings and code references
- Navigate boards - Understand your team’s area paths, iterations, and work item types
- Import work item attachments - Bring the images and documents attached to a work item into the thread, when enabled for the project
Use Cases
- Automated triage - AI agents analyze incoming bugs and suggest area paths, priority, or iteration placement
- Debug-to-work-item workflow - Convert investigation findings into properly structured Azure DevOps work items
- Sprint context - When debugging, agents understand current sprint work and related items
Work Item Attachments
PlayerZero can read the images and documents attached to a ticket, so an investigation works from the screenshots, logs, and files the ticket already carries instead of its text alone. Whether attachment import is on by default depends on when the integration was connected. Integrations connected on or after June 26, 2026 import attachments by default. Integrations connected before that date do not. To update it, open the integration’s settings, find the project, and under Ticket Attachment Settings set Mode to Allow Attachments. Choose Do Not Allow to stop importing. Only Project Owners may update this setting.The setting appears only when the integration is connected to that project.
Scopes & Permissions
PlayerZero requests only the permissions needed for AI agents to assist with work item management. We follow the principle of least privilege—each permission directly enables a specific capability.
Setup
Setup starts in PlayerZero—no pre-configuration in Azure DevOps is required.
Step 1: Start the Connection
- In PlayerZero, navigate to Settings → Context → Ticketing
- Find Azure DevOps in the available integrations list
- Click the + button to open the connection dialog
Step 2: Select PlayerZero Projects
Before connecting to Azure DevOps, you’ll choose which PlayerZero projects can use this integration:- All Projects — Every project in your organization will have access to this Azure DevOps connection. New projects added later will automatically have access.
- Custom Selection — Only the specific projects you check will have access. Use this if you have multiple teams or want to limit which projects can create or read Azure DevOps work items.
Step 3: Authorize with Azure DevOps
- Click Connect Azure DevOps to start the OAuth flow
- You’ll be redirected to Microsoft to sign in (if not already signed in)
- Review the permissions PlayerZero is requesting and click Accept
- After authorization, you’ll be redirected back to PlayerZero
Step 4: Configure Workflows (Optional)
Once connected, you can configure automated workflows for each enabled project:- Ticket routing — Automatically create work items from Player threads
- Filters — Specify which issues should trigger the integration based on title, description, or tags
Managing the Integration
After setup, you can:- Edit project access — Add or remove projects that can use this integration
- Disable/enable — Temporarily pause the integration without disconnecting
- Disconnect — Remove the integration entirely (requires re-authorization to reconnect)
Organization URL for PAT Connections
If your Azure DevOps integration uses a Personal Access Token (PAT) instead of OAuth, PlayerZero needs your organization URL to construct API calls correctly. PlayerZero attempts to detect the organization URL automatically from your credentials. If auto-detection fails, you’ll see a prompt on the integration detail page to enter it manually. Accepted formats:- Organization name:
myorg - Full URL:
https://dev.azure.com/myorg - Legacy URL:
myorg.visualstudio.com