Amplitude logo

Plan in Productboard. Build in Azure DevOps.

Push features to Azure DevOps as work items and sync fields, statuses, and hierarchy between the two.

Overview

The Azure DevOps integration connects prioritization in Productboard to delivery in Azure DevOps. Push features into Azure DevOps as work items, link work that already exists, and let field and status sync keep both systems current.

Push features as work items

Push features, subfeatures, and initiatives to Azure DevOps as any work item type — user story, bug, task, or feature. You choose the project, work item type, and area path for each push, and the feature's name, description, and mapped fields carry over. Productboard's hierarchy can be mirrored as parent-child relationships, including retroactively for already-linked work items.

Link existing work items

Connect Productboard features to work items that already exist in Azure DevOps, from a board's integration column or the feature detail view. Work in flight joins the roadmap without duplicate work items.

Sync fields both ways

Map Productboard fields to Azure DevOps fields and set the sync direction for each mapping. Feature name and description map out of the box, custom fields are supported, and with two-way sync a change in either system updates the other.

Automate status updates

Map Azure DevOps work item states to Productboard feature statuses. When a work item moves to In Progress or Done, the feature's status updates on the roadmap automatically.

Setup

Productboard admins can add the integration, and an Azure DevOps administrator completes authorization. Connections use a Personal Access Token or OAuth 2.0.

Integrations with ADO's cloud offering is supported on every Productboard plan, with the number of separate integration configurations varying by plan. Integrating with on-premise Azure DevOps Server (2018 or later) requires Productboard's Enterprise plan.

  1. Go to Settings → Integrations → Azure DevOps and click Add integration.
  2. Authorize with a Personal Access Token, or set up OAuth 2.0 through Microsoft Entra.
  3. Configure field mappings, status mappings, and optional parent-child hierarchy sync.
  4. Start pushing features or linking existing work items.

More integrations in this category