A popular terminology in Jira, an ‘Epic’ refers to a large body of work that can be broken down into smaller user stories. The Epic Linking feature replicates the parent-child relationships in other systems as epic-to-story relationships in Jira and vice versa.
When using Epic Linking, you will always have Jira on one side of the automation. The other side of the automation can be any of the following applications:
- Atlassian Jira
- Digital.ai Agility (Formerly VersionOne)
- Micro Focus ALM Octane
- Micro Focus ALM QC
- IBM Doors
- Microsoft TFS
- Microsoft Azure DevOps
- Rally Software
Epic Linking is possible in scenarios where you are linking two instances of Jira, or linking Jira and DOORS, or linking Jira and QC. To accomplish this, you'll need to create a couple of automations:
- One between the parent entities
- One between the child entities
- A custom field mapping that would complete the Epic Linking process.
This is explained in detail below, where we discuss how Epic Linking is done in some common automations.
There are a few common automation combinations that use the Epic Linking feature. Click on the links below if you are interested in learning how to set one of these up: