Parent/Epic Link/Parent Link mappings

Jira Cloud

In JIRA Cloud, the Parent field is used to implement the epic -> issue and issue -> sub-task relationships, as well as the parent-child links in Advanced Roadmaps. It replaced the Epic Link and Parent Link fields.

Parent mapping tab

If you are connecting to Jira Cloud, please use only the Parent Mapping and do not use the Epic Link, Parent Link and Sub-task mappings.

Jira Server or Datacentre

In JIRA Server/DC, the Epic Link field links issues to Epics whereas the Parent Link field is used by the Advanced Roadmaps for implementing custom hierarchy levels in plans.

Epic Link mapping tab

Parent link mapping tab

Do not use the Parent Mapping for Jira DC or Server.

Configuring Hierarchical Mappings

To change the Parent, Epic Link or Parent Link mappings, select the Parent, Epic Link or Parent Link tab in the Project settings window.

The Parent, Epic Link and Parent Link mappings are almost identical.

Field	Description
Epic (Parent) Link	Tick the option to enable the mapping
Dir	The synchronisation direction.
Parent	Tick the option to map the Epic (Parent) Link to the parent (summary) task. Import: The imported task will be placed under the task that is linked to the Epic (Parent) the imported issue is connected to. If the issue has no Epic (Parent), the new task will be created on the first level, unless there is another mapping that defines the place of the task in hierarchy. Sync (unlinked task): The new issue will be associated with the Epic (Parent) linked to the parent task of the synchronised task. If the task is on the first level, the issue will not be connected to an Epic (Parent). Sync (linked task): If the direction is from JIRA to MS Project, the task will be moved under the task that is associated with its Epic (Parent) issue in JIRA. If the issue is not a part of an Epic (does not have a Parent), it will be moved onto the first level, unless there is another mapping that defines the place of the task in hierarchy. If the direction is from MS Project to JIRA, the issue will be moved into the Epic (assigned the Parent) linked to the parent task in MS Project. If the task is on the first level in MS Project, the issue will be removed from its Epic (Parent).
Field	Tick the option to map Epic (Parent) Link to a custom text field that contains an issue key. Import: The selected field will be populated with the key of the Epic (Parent) the imported issue is a part of (assigned to). Sync (unlinked task): The new issue will be included in the Epic (assigned the Parent) with the key in the selected field. Sync (linked task): If the direction is from JIRA to MS Project, the selected field will be populated with the key of the Epic (Parent) the imported issue is a part of (assigned to). If the direction is from MS Project to JIRA, the issue will be moved into the Epic (assigned the Parent) with the key in the selected field.
Ancestor of type	Tick the option to map the Epic (Parent) Link to the first summary task up in the hierarchy whose assigned JIRA issue type satisfies the filter condition. This mapping cannot update data in MS Project. Import: Has no effect. Sync (unlinked task): The new issue will be included in the Epic (assigned the Parent) matching the first summary task up in the hierarchy whose assigned JIRA issue type satisfies the filter condition. Sync (linked task): The direction from JIRA to MS Project is not supported. If the direction is from MS Project to JIRA, the issue will be moved into the Epic (assigned the Parent) matching the first summary task up in the hierarchy whose assigned JIRA issue type satisfies the filter condition.
Ancestor on level	Tick the option to map the Epic (Parent) Link to the summary task on the selected level up in the hierarchy. This mapping cannot update data in MS Project. Import: Has no effect. Sync (unlinked task): The new issue will be included in the Epic (assigned the Parent) matching the summary task on the selected level up in the hierarchy. Sync (linked task): The direction from JIRA to MS Project is not supported. If the direction is from MS Project to JIRA, the issue will be moved into the Epic (assigned the Parent) matching the summary task on the selected level up in the hierarchy.
Only for these issue types	Tick the option and select issue types to apply the mapping only to particular issue types. When data is copied from JIRA to MS Project, the issue type comes from JIRA. When data is copied from MS Project to JIRA, the issue type is the value of the field Issue Type is mapped to using the Issue Type mapping.