Short definition
Epic Link is the Jira field that connects a story, task, or bug to its parent epic. On Jira Data Center it's a dedicated custom field named 'Epic Link.' On Jira Cloud the same relationship is expressed via the standard `parent` field after the platform's hierarchy refactor. Either way, Epic Link is how child issues roll up to an epic for reporting, burndown, and roadmapping.
What Epic Link does
Epic Link is the data backbone of every epic-level report in Jira:
- Epic Burndown counts story points of issues sharing an Epic Link to forecast completion.
- Roadmap / Plans views group issues under their epic via Epic Link.
- Boards with epic-based swimlanes use Epic Link to assign each issue to its lane.
- JQL queries like
"Epic Link" = ABC-123orparent = ABC-123return all child issues.
Without an Epic Link, an issue is “orphan work” - it’ll appear on boards and filters but won’t roll up to
any epic’s reporting. Most teams have a small backlog of orphan issues that should be assigned to an
epic but aren’t; auditing for "Epic Link" is EMPTY AND issuetype in (Story, Task) is a useful periodic
cleanup query.
The Cloud vs. Data Center difference
Two important nuances:
- On Jira Data Center, Epic Link is a separate custom field from
parent. The parent field is used for sub-task-to-standard-issue relationships; Epic Link is used for standard-issue-to-epic. They’re conceptually similar but stored separately. - On Jira Cloud, Atlassian unified the hierarchy under the
parentfield. A sub-task’s parent is its standard issue; a standard issue’s parent is its epic. The legacy Epic Link field name still works in many UIs and JQL queries as a synonym, but new tooling should preferparent.
This split causes occasional confusion when migrating between Cloud and Data Center, and when integrating tools that target one but not the other.
Setting Epic Link
Three ways:
- From the issue view - the Epic Link / parent field is editable in the right-hand panel.
- From the backlog - drag an issue onto an epic in the epic panel; Jira sets the link.
- Via JQL bulk edit - select issues in the navigator, Tools -> Bulk Change, Edit issues, set Epic Link.
For automated parent-assignment (e.g., new bugs in a component automatically link to a specific epic), an automation rule with trigger Issue Created and action Edit Epic Link is the standard pattern.
Common questions
What is the Epic Link field in Jira?
Epic Link is the Jira field that connects a story, task, or bug to its parent epic. On Jira Data Center it's a dedicated custom field named 'Epic Link.' On Jira Cloud the same relationship is expressed via the standard parent field after the platform's hierarchy refactor. Either way, Epic Link is how child issues roll up to an epic for reporting, burndown, and roadmapping.
Epic Link vs. parent - is there a difference?
Historically yes, currently mostly no. Data Center kept Epic Link as a separate field while sub-tasks used a separate parent field. Cloud unified both under the parent field. JQL on Cloud uses `parent = ABC-123` for both relationships; on Data Center, `"Epic Link" = ABC-123` is still the dominant syntax.
Can an Epic Link cross projects?
On Jira Cloud, yes - the parent field can reference an epic in a different project. On Data Center the Epic Link field is project-scoped by default, so cross-project epic relationships are usually modelled via Issue Links (`is part of` / `relates to`) or Advanced Roadmaps. Check your Jira version before designing cross-project epic structures.
How do I bulk-update Epic Link?
Use Jira's bulk-edit (Tools -> Bulk Change from any issue navigator), with the source filter selecting the issues to re-parent. Bulk-edit can set Epic Link in one action. For automation, an automation rule with trigger 'manual' and action 'Edit issue field: Epic Link' lets non-admins re-parent issues without touching admin UI.