All Collections
AzureDevOps and TFS
Dependency Creation and Tracking for AzureDevOps Boards
Dependency Creation and Tracking for AzureDevOps Boards

Set target dates, custom workflow and rich text area to capture details

Kendis Team avatar
Written by Kendis Team
Updated over a week ago

For AzureDevOps boards the dependency experience is completely redesigned.

The major upgrades include more intelligent, visually better representation, with smarter filtration and sorting options.

1. Defining New Dependency Parameters

The create and edit view is redesigned and it offers more options to capture details and track them.

Dependency Creation and Edit Details

Link Type and Status

Kendis provides you with a color-coding system to make the visual representation of your dependencies more powerful and meaningful.

Primarily on the spectrum of Open to Resolved, the Dependency Colour shifts as a statement of the treatment offered to the dependency. The Dependency Colour is assigned when defining the Link Type and can be updated as the status of the dependency changes from Open to Resolved.

The dependency status is significant as it tracks the Link Type along with documenting the workflow.

To explain this further, consider a scenario where the following dependency is created and Status is marked: Waiting for Acceptance.

The system is smart to show you the warnings.

If you are making dependencies in the reverser order, e.g., feature 101 is in Sprint 3 and it can't be a "Successor" to feature 7, which is in Sprint 2.

If you change the link type to "Predecessor" in this example then the warning will go away.


The new Dependency view for Azure/TFS Boards at Kendis provides a comprehensive streamlining of the historical data. There are three kinds of time stamps provided for defining your dependencies:

Raised On: This section registers the date on which the dependency has been reported.

Target Resolution Date: Assigning a target resolution date to a dependency optimizes your team’s target documentation and adds transparency.

Updated on: This section documents the date of the latest status change of the dependency.

Roles: Reporter, Responsible, and Watched by

Identify the Reporter as well as the Responsible for the dependency to keep the action responsibility a part of the reporting process. This helps in maintaining an SSoT (single source of truth) for your teams.

Watched by section ensures that all the members interested in the resolution of a certain dependency stay updated by notifications of each status update of the dependency.


Summary: The summary section records the operational identification of your dependency.

Description: Kendis provides you with a rich text editor to document in entirety the details of your dependencies. Attach multimedia, format, and use the calendar plugin to make your dependency descriptions wholesome and complete.

Conversations: This section allows organized, structured team communication to collaborate on each dependency. Tag your team members and discuss your solutions.

Save your data after setting your dependency parameters, before exiting the view.

  1. Dependencies List View

The new Dependency List View empowers you to:

Edit your dependencies

Change the parameters of your dependency, or delete it from your list view as your needs evolve.

Sort dependencies by different orders

Display your dependency sorting by visualizing according to your preferred order.

Filter the Dependency list view

Filter your dependencies using a list of options to eliminate the irrelevant dependencies from your list view.

Did this answer your question?