| Table of Contents |
|---|
Purpose of this page
The purpose of this page is to provide clarity| Excerpt | ||
|---|---|---|
| ||
We shed light on how we define a Jira ‘dependency’ that is captured in the Dependency Mapper for Jira app. |
| Table of Contents |
|---|
What is the definition of a dependency?
When we talk about a dependency, it is based on the scenario where an item of work (e.g. Story, Task, Epic etc.) can not be resolved until another item of work has been resolved prior. The ‘dependency’ is the linkage, or relationship, between those two work items.
What are the elements of a dependency within Jira?
In the context of Jira, more specifically the Dependency Mapper for Jira app, there are three key elements that we use to identify a dependency
The Jira issue that raised the dependency, or the issue that is dependent on another issue in some way
The Jira issue that received the dependency, or the issue that must be resolved before the dependent Jira issue can also be resolved
The type of dependency recorded, or the Issue Link type that was used to identify the dependency in Jira
