Board
Overview
Build Options control how Work Items are sourced and how timelines are generated on the Roadmap. These settings determine the scope of data included and how dates are interpreted, helping ensure your roadmap accurately reflects your planning approach.
Use Cross Project Queries (Pro Feature)
Enable Cross Project Queries to include Work Items across multiple Projects based on your access.
- Work item scope: Only work items in Projects where you have access are counted.
- Children visibility: Children of selected Work Items from other Projects will also appear on the view.
- Build By Query: Automatically detects cross-project queries and fetches Work Items from accessible Projects.
Not supported in Azure DevOps Server 2019.
Build Mode
Hybrid
Builds Timelines using a combination of Iteration Path dates and StartDate/TargetDate fields.
Best for: When you need high-level planning at the Epic level while still reflecting real execution through Iterations on child Work Items.
Example: Product leadership sets quarterly target dates on Epics, while delivery teams plan Features and User Stories into sprints.
Generated
Builds Timelines using the Iteration’s defined start and end dates.
Best for: When you want to reflect what is actually planned and tracked in Azure DevOps.
Example: Sprint planning is finalized and you want the roadmap to mirror the exact iteration schedule and completed work.
Manual
Builds Timelines using the StartDate and TargetDate fields directly from the Work Item.
Best for: When timelines are not fully defined and you need to quickly estimate or plan at a high level.
Example: Early roadmap planning where dates are approximate and not yet broken down into iterations.
For a Work Item to appear on the Roadmap, the required fields must be set. Iteration for Generated mode, or StartDate/TargetDate for Manual mode.