Skip to main content
System StatusContact Support
VersionOne Community

Dependencies

This feature is available in Enterprise and Ultimate editions.

editions-eu.png

This article describes how set and identify work item dependencies.

dependencies_workitems.png

Adding Dependencies

Option 1. From the Grid (Fastest)

  1. On the Product Planning > Backlog page, select item(s) with a dependency using the checkbox.

  2. Select Dependencies > Assign Upstream Dependencies or Assign Downstream Dependencies.

  3. Select the appropriate item(s), and then click Add.

Option 2: Details Page

  1. Open a story/defect/test set and scroll to the bottom of the window, and then click Manage Relations.

  2. Click the Assign button to the right of the Upstream Dependencies or Downstream Dependencies grid.

    dependencies_assign.png

  3. In the pop-up window, click Add next to each item you want to add as a dependency.

  4. Click Close Window to return to the details page..

Viewing Dependencies

Option 1. In Release Scheduling and Sprint Scheduling Grids

You can also see dependencies in the Release Scheduling and Sprint Scheduling grids by adding the following columns to the grid. Note that these columns are hidden by default.

  • 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).

    DependenciesGrid.jpg

Option 2. On the Details Page

To see dependencies for a specific backlog item, open the Story Details page, and then click Downstream Dependencies or Upstream Dependencies. The dependencies grid will display the dependent relationships.

dependencies_downstream.png

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.

Key Points

When setting up dependency relationships in VersionOne, 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