With productboard's Azure DevOps integration, you can use the productboard to collect customer feedback, prioritize what to build next, and align with everyone using roadmaps while product teams use Azure DevOps for their day-to-day delivery.
Push prioritized features and subfeatures into Azure DevOps where they can be managed through the delivery process.
- Push productboard features as Azure DevOps work items (Epics, Issues, Features, Tasks, User Stories, Product backlog items, etc., based on your Azure DevOps Board setup).
- Push productboard subfeatures as Azure DevOps work items (Tasks, User Stories, Product Backlog items, etc., based on your Azure DevOps Board setup).
- Easily navigate back to the associated feature or subfeature in productboard with an auto-generated productboard URL link added to Azure DevOps work items (accessible via work item link section or in comments).
- Support for multiple Azure DevOps projects: Opt to select an Azure DevOps project each time you push a feature.
- Support for multiple Azure DevOps instances: Set up multiple Azure DevOps integrations in the same productboard workspace. You can even push the same feature to multiple Azure DevOps instances.
- Support for Azure DevOps Server: Integrate with an instance of Azure DevOps you are self-hosting. More info
Configure your Azure DevOps Integration
(You will need Azure DevOps Administrator Permissions and be a Productboard maker with admin access to follow the steps below.)
Authorize the integration:
- In productboard, use the bottom left menu to select Integrations.
- Beside Azure DevOps, select [+] to add a new integration.
- Follow the directions provided to complete the authorization.
Default field mappings between features/issues
When features/subfeatures are pushed into Azure DevOps, their fields are mapped to Azure DevOps in the following way:
productboard | Azure DevOps
- Feature name | Work item name
- Feature description | Work item description
- Productboard Feature Link | Work Item Links Section & Comment containing the URL linking back to Productboard
Note: The assignee/owner field is left blank so it can be filled out in Azure DevOps.
Deactivate the Azure DevOps integration
To deactivate the integration, in productboard, on the Integrations page, toggle off the integration in question.
Remove the Azure DevOps integration
You can permanently remove the Azure DevOps integration at any time from the integration's settings page in the productboard. Select Remove in the upper right.
Azure DevOps Services (Cloud / On-demand) vs Azure DevOps Server (Self-managed / On-Premise)
Follow these steps if you are using Azure DevOps Server:
Not sure which product your organization has?
How the Azure DevOps integration works
Push prioritized features straight into development
Once the Azure DevOps integration is enabled, you can push a feature into Azure DevOps in its details side pane.
You can also display a special Azure DevOps task column on your boards:
The Azure DevOps task column allows you to easily push many features into Azure DevOps.
At the moment you push a feature into Azure DevOps, you can decide its project and work item type. This can be always updated later in your Azure DevOps board.
Features in productboard are typically pushed to Azure DevOps as Features but you can choose any work item type you want depending on your board setup (Basic, Agile, Scrum, CMMI, or Custom).
- In some cases you may have small, yet important, ideas represented as features in productboard. These can be pushed to Azure DevOps as user stories, bugs, tasks, or other custom work item types.
- Even after pushing a feature to Azure DevOps, you can always update its work item type in Azure DevOps.
Once features are pushed, whether, from the details pane or task column, you'll see the work item's ID displayed (on hover). Select this to navigate to the work item in Azure DevOps. (You can use the productboard URL field in the work items link section to navigate back to features in productboard.)
Navigate back to features in productboard from Azure DevOps:
Pushing subfeatures into Azure DevOps
Subfeatures can be pushed into Azure DevOps in the same way as features.
Subfeatures are typically pushed to Azure DevOps as user stories, product backlog items, issues, or features (depending on your Azure DevOps board setup).
- Subfeatures can also be pushed as bugs, tasks, subtasks, or other custom work item types.
- No feature <> subfeature relationship (parent, sibling, etc.) will be carried over to Azure DevOps.
- Even after pushing a subfeature to Azure DevOps, you can update it to a feature later. You can also always update its work item type in Azure DevOps.