# Dependencies

The Dependencies view provides an interactive map of all issue links in your project. It helps you identify bottlenecks, date conflicts, and critical paths at a glance.

## Interactive Map

Issues are displayed as nodes connected by directional arrows representing Jira issue links (e.g., "blocks", "is blocked by", "relates to"). The map supports:

* **Pan** -- click and drag the background to navigate the map
* **Zoom** -- scroll to zoom in or out, or use the zoom controls

The layout adjusts automatically based on the number of nodes and their connections.

## Conflict Detection

The Dependencies view analyzes scheduling data to highlight problems:

* **Red indicators** -- date conflicts where a blocking issue ends after the blocked issue starts
* **Orange indicators** -- critical path items where delays would cascade to dependent work

This makes it easy to spot scheduling issues that need attention before they become blockers.

## Grouping

You can group nodes visually by different fields to understand how dependencies flow across organizational boundaries:

* **Area** -- group by component or area
* **Team** -- group by team field
* **Parent** -- group by parent issue in the hierarchy
* **Sprint** -- group by sprint assignment
* **None** -- flat layout with no grouping

## Dependency Table / Ledger

Below the map, a tabular ledger lists every dependency relationship in the project. Each row shows:

* Source issue (key and summary)
* Link type
* Target issue (key and summary)
* Date conflict status

This table is useful for reviewing dependencies in bulk and for teams that prefer a list format.

## Filters

The Dependencies view respects all toolbar filters. Additionally, you can filter by **role** to show only issues that are blockers, only blocked items, or both.

## Adding Dependencies

Use the **+ New relation** button in the toolbar to create a new issue link directly from the Dependencies view. Select the source issue, link type, and target issue to add the dependency without leaving the map.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hiera.gitbook.io/hiera-docs/views-and-features/dependencies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.