This feature is available in Enterprise and Ultimate editions.
Option 1. In Release Scheduling and Sprint Scheduling Grids
- Upstream Dependencies - Shows that other stories must be completed before the current story can be completed
- Downstream Dependencies - Shows stories that are dependent on the completion of the current story
- Dependency Status Icon - Indicates that the dependency is satisfied, broken, or overlapping (as the dependencies change during the course of a sprint/iteration, status icon changes to reflect the status).
Option 2. On the Details Page
To see dependencies for a specific story, open the Story Details page, and then click Downstream Dependencies or Upstream Dependencies. The dependencies grid will display the dependent relationships.
Option 3. Dependency Visualization Reports
These dependency reports allow you to view all active dependencies defined in a project or program. Reading from left to right, they show the sequence necessary to deliver stories, defects, test sets, and portfolio items (respectively) in a dependency chain.
When setting up dependency relationships in Lifecycles, here are a few important things to understand:
Primary workitems can have an unlimited number of dependency relationships.
Dependency status is evaluated using the sprint dates for each item. This allows you to evaluate dependencies assigned to different teams or projects.
Dependencies can have three states:
Green - Satisfied: dependencies exist and are being satisfied by the current sprint scheduling
Yellow - Warning: dependencies exist and the sprints in which they are scheduled overlap
Red - Broken: dependencies exist and are broken by the current sprint scheduling