Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure DevOps Services | Azure DevOps Server | Azure DevOps Server 2022
Delivery Plans provide visual dependency tracking for work items linked with Predecessor/Successor relationships. Dependency visualization helps you identify scheduling conflicts and manage cross-team dependencies effectively.
Cards display dependency status icons:
Green icon: No dependency scheduling issues
Red icon: Dependency scheduling conflicts detected
Prerequisites
| Requirement | Description |
|---|---|
| Access | Member of the Project Collection Valid Users group or Stakeholder access |
| Permissions | Edit work items in this node permission set to Allow for relevant Area Paths |
| Configuration | Delivery Plan created with teams and backlogs configured |
| Dependencies | Work items linked using Predecessor-Successor link type |
For complete setup requirements, see Add or edit a Delivery Plan.
Tip
You can create dependencies between work items across different projects and teams within the same organization. Dependencies across organizations aren't supported.
View dependency lines
Open your Delivery Plan from Boards > Delivery Plans.
Select the top or bottom edge of a work item card to show its dependency lines. Select again or select elsewhere to hide the lines.
No scheduling conflicts (black lines):
Scheduling conflicts (red lines):
Tip
Expand both team rows to see dependency lines across teams.
To view conflict details, select the
issue icon on the work item card.
View dependency details
For detailed dependency information, select the dependency icon (
or
) on any work item card.
The Dependencies dialog shows:
- All predecessor and successor work items
- Dependency status and any scheduling conflicts
- Cross-project dependencies (when applicable)
Resolve dependency conflicts
Dependency conflicts occur when a successor work item is scheduled to complete before its predecessor. These conflicts appear with red indicators in the Dependencies dialog.
To resolve conflicts:
- Review scheduling: Check the Target Date or Iteration Path end dates for conflicting work items
- Adjust timing: Modify work item dates or iteration assignments to resolve scheduling conflicts
- Re-evaluate dependencies: Consider if dependency relationships are still accurate
Note
Dependency end dates are determined by either the work item's Target Date or the End Date of its assigned Iteration Path.
Best practices for dependency tracking
- Use consistent link types: Always use Predecessor-Successor links for dependency tracking
- Regular review: Check dependency status during sprint planning and reviews
- Cross-team coordination: Expand team rows to visualize dependencies across teams
- Proactive management: Address red dependency indicators promptly to avoid delays