Skip to main content
Description of the dependency line colors

What each color means, how it's related to type of dependency and it's status

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

On your Kendis board, dependency lines are displayed in various colors. Each color has a specific significance, so understanding what each one represents is crucial. Dependency line colors on the Kendis board can differ depending on their origin. Lines representing dependencies created directly on the Kendis board may have different colors compared to those brought from agile tools such as Azure DevOps or Jira.

Line Color

Dependency Status

Description

Open Dependency:

Dependency Status is in 'To Do' or 'In Progress' status category.

A dependency created on the Kendis board is currently open. Teams need to address and resolve it before the due date or the end of the sprint.

Resolved Dependency: Dependency status is in the ' Done ' status category

A dependency can automatically be marked as done if the target or source item is in the 'Done' status category. By default, this option is not enabled, so ensure you activate it in the settings.

Resolved Dependency (past due date):

Dependency status is in the ' Done ' status category

When a dependency is marked as 'Done' after the due date set in the dependency or the sprint date of the dependent card, its color changes to turquoise instead of green. This helps visualize and filter dependencies that missed their original due dates.

Open Dependency Moved

If the receiver card (dependent item) of a dependency changes its team or sprint, the dependency line will turn yellow. It will remain yellow as long as the dependency is in the 'To Do' or 'In Progress' status categories."

Open dependency (past due date):

Dependency status is in 'To Do' or 'In Progress'

The red color identifies dependencies that have missed their due date or the sprint date of the dependent cards in the past. This helps visualize and filter dependencies that missed their due dates.

Reverse Dependency: Received/ Dependent item is in the future sprint

A reverse dependency occurs when the dependent/receiver card is in a future sprint. This means the necessary work cannot be completed yet because it is scheduled for a future sprint. You can use filters to identify these dependencies.

ALM Open Dependency: Created in Agile tool and pulled into Kendis board and is 'To Do' or 'In Progress' status category

If a dependency is created in your Agile tool (Azure DevOps or Jira) and is in Open status, it will be displayed in blue. Blue line dependencies do not have a creator, responsible, or other values when you edit them. You can set these values during the editing process.

ALM Resolved Dependency: Created in Agile tool and pulled into Kendis board and is 'Done' status category

When an ALM dependency (originally in blue) is moved to the 'Done' status category, it will be displayed in a this shade of green.

How to Filter Dependencies List by Color

You may filter dependencies based on their line colors. For example, to find dependencies that have missed their due dates and are still open, select the red color, and the relevant dependencies will be displayed.

To filter the dependencies:

  • Click on "More" and select "Dependencies."

  • Under the more filters option, check the "By Color Type" option.

  • Select the color you wish to filter by and press the “Update Filter” button.

  • Kendis will now display the results for this specific color.

  • It is also possible to select multiple colors and apply a filter.

Did this answer your question?