How to use Issue Links and Epic Links
This page introduces Jira issue links and epic links and describes how and when to use them.
Before we get started there is one important point to acknowledge...if epics are just another type of issue, why do they get their own link type? And, can't we just use standard issue links with epics?
Most issue types in Jira work exactly the same. Whether you are in a task, coding task, configuration task, etc., all of these issue types work the same. Epics, however, have additional meaning and functionality in Jira.
First, let's determine the differences (and similarities) between issue links and epic links.
Issue Links
Issue links can be made between any issue type. These are the available link types. See the descriptions below.
When making issue links, it is important to get the direction correct. For example, for the Blocks link type, one issue is the blocker ("blocks") and the other is the block-ee ("is blocked by"). There are many dashboards, reports, and filters that use the direction of the links, so it is important that the links be created in the proper direction.
To create a link between two issues, go to "More"..."Link".
Blocks
Blocks is used when you want to indicate that one issue is preventing another issue from being resolved. The issue that has to be done first blocks the second issue, and the second issue is blocked by the first.
Cloners
Cloners is automatically used by Jira when an issue is cloned. This link type should only be used by Jira during the cloning process.
Duplicate
Duplicate is used when one issue is the duplicate of another. Typically, one of the issues will be canceled, and the other will remain open until resolved.
Implements
Implements is used in the Initiative/Epic relationship. Epics implement Initiatives, and Initiatives are implemented by Epics.
Problem/Incident
Problem/Incident is not currently used. If we develop a problem management system, we will use this then.
Relates
Relates is the most generic link type. Use it to link any two issues that are related to each other. Many times, relations are obvious. For example, if the two issues are in the same epic, they are clearly related, and the link is not required. This is most often used when it is helpful to know of the relationship, but the relationship is not obvious.
Remediation
Remediation links are used between ITSD tickets and the tickets representing the work to resolve them. For more information, see JSDV2 Remediation Issues for Service Requests.
Epic Links
(to be written...in the meantime, see: https://www.atlassian.com/agile/project-management/epics)