Azure DevOps

Want the overview first? See the Azure DevOps integration overview.

Ybug creates a work item in Azure Boards for every report it forwards. It works with Azure DevOps Services (dev.azure.com) and with Azure DevOps Server, as long as the server is reachable from the internet.

Create a personal access token

Ybug connects to Azure DevOps with a personal access token (PAT).

1. In Azure DevOps, open User settings (the icon next to your avatar) → Personal access tokens and click New Token.

2. Under Organization, pick the organization Ybug should create work items in. Azure DevOps Server has no organization picker, so skip this step there.

3. Set an expiration date. Azure DevOps allows at most one year.

4. Under Scopes, choose Custom defined and select:

• Work Items: Read & write
• Project and Team: Read

5. Click Create and copy the token. Azure DevOps shows it only once.

How to set up

Configuration is per-project in Ybug. To integrate your Ybug project with Azure DevOps, go to your dashboard and follow these steps:

1. Go to the Integrations section in your project settings.

2. Click the On/Off switch in the Azure DevOps row.

3. Tell Ybug where your Azure DevOps lives:

• Azure DevOps Services: enter your organization name, the part after dev.azure.com/. For https://dev.azure.com/acme, that's acme.
• Azure DevOps Server: enter the full collection URL, for example https://tfs.example.com/DefaultCollection. The address must use HTTPS and be reachable from the internet. Ybug can't connect to a server behind a firewall or on a private network.

4. Paste your personal access token and click Authenticate with Azure DevOps.

5. Choose where new work items go, then click the Save settings button. Use the Test button to send a sample report.

• Project: the Azure DevOps project for new work items.
• Work item type: Ybug picks Bug when the project has it, and Issue in projects on the Basic process. You can choose any enabled type.
• Area: defaults to the project's root area.
• Iteration (optional): leave it empty to put work items in the project's root iteration.
• Assignee (optional): members of the project's default team.

What the work item contains

• Title: the report title, using the title format from Advanced settings.
• Repro Steps when the work item type has it, Description otherwise: the reporter's comment and the forwarded data, with the screenshot shown inline.
• Attachments: the console log if you switch on Attach console log in Advanced settings, and the screenshot as a file if you switch on Attach screenshot.
• Links: a hyperlink back to the original Ybug report.
• Tags: ybug, plus the tags of the Ybug report.
• Priority: Ybug's default priorities map to Azure DevOps priority 1 (Highest) to 4 (Low and Lowest). Custom priority names leave the Azure DevOps default in place.

Changes you make to the work item in Azure DevOps don't sync back to Ybug.

Don't see the Bug on your board?

The work item is there: you'll find it under Boards → Work items. Whether it appears on a board depends on your Azure DevOps team settings.

Bugs are tracked with tasks. In Agile, Scrum and CMMI projects, a team can track bugs as requirements or as tasks. Bugs tracked as tasks show up only on the sprint Taskboard, never on the Kanban board. To change this, open Project settings → Team configuration, pick your team and, under Working with bugs, choose Bugs are managed with requirements. If it's set to Bugs are not managed on backlogs and boards, bugs don't appear on any board.

The area belongs to another team. Each team's board shows only the work items in that team's areas. The Area you choose in Ybug decides which team's board the work item lands on. Check the team's areas in Project settings → Team configuration → Areas, including whether sub-areas are included.

Projects on the Basic process don't have this setting: Issues always appear on the board.

When the token expires

When Azure DevOps stops accepting the token, Ybug pauses the integration and emails you. Create a new token, click Change next to the connected account in the integration settings, reconnect with the new token, and save the settings.

Required fields

If your process makes a field required on the chosen work item type and the field has no default value, Azure DevOps rejects the work item. Ybug then pauses the integration and emails you the field name. Make the field optional or give it a default value in your process, then save the integration settings again.

Advanced settings

Click Advanced settings in the integration form to change how the created work item looks.

Work item title format: the default is [{{project.name}}] #{{report.id}} {{report.title}}, and you can compose your own from placeholders such as {{report.priority}} or {{report.user.email}}. See Title format for the full list.

Forwarded data: choose which details Ybug includes, from the source URL and the reporter to browser, screen size and custom user data. See Forwarded data for all the options.