The integration between Azure DevOps and Forecast allows developers to collaborate with other teams and access information held in distributed systems in the end-to-end software delivery value stream. This is achieved by Forecast's ability to seamlessly sync projects and their components between the two platforms. If you are looking to install the integration, see Setting up the Azure DevOps integration for Forecast instead.
This article includes:
- Understanding the data flow between Azure DevOps and Forecast
- Azure DevOps and Forecast's task hierarchy limitations
- Connecting Forecast projects to Azure DevOps
- Setting up the Azure DevOps integration for Forecast
- Importing users from Azure DevOps
Understanding the data flow between Azure DevOps and Forecast
Data synchronization between Azure DevOps and Forecast
The table below shows how data flows between the two platforms. All of the data points in the connection are bi-directional.
|Phase||<->||Feature or Epic|
Data synchronization on Tasks/Work items
The table below shows how tasks/work items data is synced between the two platforms. Most of the data points in the connection are bi-directional.
|Start Date||<->||Start Date|
|Sum of time registrations||->||Completed work|
|Estimate||<->||Chosen ADO Field|
Work item types synchronized to Forecast
Currently only the following Azure DevOps work item types are synchronized as tasks in Forecast:
- Product Backlog Item
- User Story
- Bug (depending on the 'Sync bugs in ADO' setting on project)
Azure DevOps work items of type 'Task' will be synchronized to Forecast as sub-tasks only if they have a parent work item in Azure DevOps that is synchronized to a Forecast Task.
Azure DevOps and Forecast task's hierarchy limitations
If Task Hierarchy is enabled in Forecast, there are certain limitations to be aware of when moving DevOps-linked tasks in the hierarchy in Forecast:
- Moving a Forecast task under another Forecast task will have no effect in DevOps and will not change the issue type of a task.
- Moving a sub-task under another task/sub-task in Forecast also has no effect in DevOps.