Issue Type Hierarchy with Advanced Issue Sync

Overview

Jira supports issue hierarchies that extend above and below the Epic level. For example, a project may use the following structure:

CODE

Highlight
  └── Feature
        └── Epic
              └── Task / Story / Bug
                    └── Sub-task

Advanced Issue Sync can sync this full hierarchy across Jira instances, including between Data Center and Cloud environments. The hierarchy is represented differently depending on the platform:

Platform	Below Epic (Task → Epic)	Above Epic (Epic → Feature → Highlight)	Sub-task → Parent
Data Center	`epicLink` custom field	`parentLink` custom field	Native `parent` field
Cloud	`parent` field	`parent` field	`parent` field

Supported Hierarchies

Advanced Issue Sync supports syncing across all combinations:

Source	Target	Hierarchy Support
DC	DC	Full — both `epicLink` and `parentLink` custom fields
DC	Cloud	Full — DC fields mapped to Cloud's single `parent` field
Cloud	Cloud	Full — native `parent` field
Cloud	DC	Full — Cloud `parent` mapped to DC custom fields

Configuration

Data Center to Data Center

Both source and target require the parentlink custom field ID in addition to the existing epiclink and epicname fields.

YAML

serverfrom:
  iscloud: false
  customfields:
    epiclink: customfield_10109
    epicname: customfield_10105
    parentlink: customfield_10101    # ← required for hierarchy sync
  issuetypes:
    subtask: 10003
    task: 10002
    epic: 10000
    feature: 10400                   # ← map above-epic types
    highlight: 10401

serverto:
  iscloud: false
  customfields:
    epiclink: customfield_10109
    epicname: customfield_10105
    parentlink: customfield_10101    # ← required for hierarchy sync
  issuetypes:
    subtask: 10003
    task: 10002
    epic: 10000
    feature: 10400
    highlight: 10401

Data Center to Cloud

The source requires parentlink; the target does not need it (Cloud uses the native parent field for all hierarchy levels).

YAML

serverfrom:
  iscloud: false
  customfields:
    epiclink: customfield_10109
    epicname: customfield_10105
    parentlink: customfield_10101
  issuetypes:
    subtask: 10003
    task: 10002
    epic: 10000
    feature: 10400
    highlight: 10401

serverto:
  iscloud: true
  issuetypes:
    subtask: 10008
    task: 10007
    epic: 10000
    feature: 10009
    highlight: 10012

Cloud to Cloud

No custom field configuration needed — Cloud uses the native parent field.

YAML

serverfrom:
  iscloud: true
  issuetypes:
    subtask: 10003
    task: 10002
    epic: 10000
    feature: 10400
    highlight: 10401

serverto:
  iscloud: true
  issuetypes:
    subtask: 10008
    task: 10007
    epic: 10000
    feature: 10009
    highlight: 10012