Skip Ahead to:<\/strong><\/p>\n Overview<\/a><\/p>\n Navigation<\/a><\/a><\/a><\/p>\n Create Dependency Link<\/a><\/p>\n Remove Dependency Link<\/a><\/p>\n Highlight All Interdependent Cards<\/a><\/p>\n Highlight All Direct Dependent Cards<\/a><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n The dependency view in the Work Hub helps you keep track of all the activities dependent on each other in a project. Unlike the dependency view of a card, the dependency view in the Work Hub helps to view all the activities’ dependencies collectively.<\/p>\n The card which is dependent on the other card is called the successor and the card on which the other card is dependent is called the predecessor. The dependency link represents dependency between the activities. This link is seen from the predecessor card to the successor card. <\/a>Navigate to the top breadcrumb, hover over the Project name, expand the Execute<\/strong> module, and select Work Hub.<\/strong><\/p>\n <\/a>To create a dependency link between two cards, draw a line from the predecessor to the successor card.<\/p>\n <\/a>To remove a dependency link between cards, click the link (which you want to delete). Click the Remove Dependency\u00a0<\/b>icon.<\/p>\n A subnet (neighborhood) is a set of cards on the board that has dependencies among themselves. On creating dependency links between two or more cards, a subnet is formed.<\/p>\n <\/a>Clicking the\u00a0Highlight All Interdependent Cards<\/b> icon highlights all the cards of the subnet and defocuses the rest cards.<\/p>\n Highlight Direct Dependent Cards<\/strong> icon highlights the cards that are linked to the cards of the current Link and defocus the rest cards.<\/p>\n The color of the dependency icon and the link is decided according to the given conditions \u2013<\/p>\n 1) If a workitem has no dependency links (relations) with any workitem, then the color of the dependency icon on this workitem will be grey in color.<\/p>\n 2) If a workitem has a dependency on a workitem and any of the four fields (Done date, Due date, Sprint date, and Release date) are available on both the workitems (predecessor and successor), then the color of the dependency links and icon on both the workitems will be decided by comparing the dates of the following fields on the workitems in the given order \u2013<\/p>\n 3) Green Color –<\/strong> <\/span>If the value of a predecessor field is before the value of the successor field then it is an ideal scenario and hence the color of the dependency icon and dependency links between the cards is green.<\/p>\n 4) Red Color –<\/strong><\/span> If the value of a predecessor field is after the value of the successor\u2019s field then the color of the Dependency icon and links will be red.<\/p>\n 5) Grey Color –<\/strong><\/span> If there are dependency links (relation) on a workitem, and the value of any of the fields (Done date, Due date, Sprint date, and Release date) is not available then the dependency icon and link color will be grey.<\/p>\n 6) If there are multiple dependency links on a workitem and any of them is red then the dependency icon on the workitem will be red.<\/p>\n 7) If all the dependency links on a workitem are green then the dependency icon will be green.<\/p>\nOverview<\/h2>\n
\nNote: <\/b>The Dependency View is only available for software templates.<\/a><\/a><\/p>\n![\"Dependency](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/Dependency-View-1.png\")
<\/p>\nNavigation<\/h2>\n
Create Dependency Link<\/h2>\n
![\"\"](\"https:\/\/www.nimblework.com\/knowledge-base\/nimble\/wp-content\/uploads\/2022\/03\/DependencyLink.png\")
<\/a><\/p>\nRemove Dependency Link<\/h2>\n
Highlight All Interdependent Cards<\/h2>\n
Highlight Direct Dependent Cards<\/h2>\n
Color of the Dependency Links and Dependency Icon<\/h3>\n
\n
\n
\n
\n