You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/boards/plans/track-dependencies.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,12 +18,12 @@ ms.date: 09/03/2025
18
18
19
19
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.
20
20
21
-
:::image type="content" source="media/dependencies/dependencies-with-without-issues.png" alt-text="Screenshot of delivery plan showing work items with dependencies and dependency issues.":::
:::image type="content" source="media/dependencies/dependencies-with-without-issues.png" alt-text="Screenshot of delivery plan showing work items with dependencies and dependency issues.":::
26
+
27
27
## Prerequisites
28
28
29
29
| Requirement | Description |
@@ -40,9 +40,9 @@ For complete setup requirements, see [Add or edit a Delivery Plan](add-edit-deli
40
40
41
41
## View dependency lines
42
42
43
-
1.[Open your Delivery Plan](add-edit-delivery-plan.md#open-plans) from **Boards** > **Delivery Plans**.
43
+
1. Open your Delivery Plan from **Boards** > **Delivery Plans**.
44
44
45
-
2. Select the top or bottom edge of a work item card to show its dependency lines. Select again or click elsewhere to hide the lines.
45
+
2. 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.
46
46
47
47
**No scheduling conflicts** (black lines):
48
48
:::image type="content" source="media/dependencies/dependency-lines-no-issue.png" alt-text="Screenshot of dependency lines showing no scheduling issues.":::
@@ -78,9 +78,9 @@ Dependency conflicts occur when a successor work item is scheduled to complete b
78
78
79
79
**To resolve conflicts:**
80
80
81
-
1.**Review scheduling**: Check the **Target Date** or **Iteration Path** end dates for conflicting work items
82
-
2.**Adjust timing**: Modify work item dates or iteration assignments to resolve scheduling conflicts
83
-
3.**Re-evaluate dependencies**: Consider if dependency relationships are still accurate
81
+
-**Review scheduling**: Check the **Target Date** or **Iteration Path** end dates for conflicting work items
82
+
-**Adjust timing**: Modify work item dates or iteration assignments to resolve scheduling conflicts
83
+
-**Re-evaluate dependencies**: Consider if dependency relationships are still accurate
84
84
85
85
> [!NOTE]
86
86
> Dependency end dates are determined by either the work item's **Target Date** or the **End Date** of its assigned **Iteration Path**.
0 commit comments