Sub-task mapping

The Sub-task mapping allows synchronising the sub-task hierarchy in Jira Server or DC with MS Project. For Jira Cloud, please use the Parent Mapping instead.

To change the sub-task mappings, select Sub-tasks tab in the Project settings window.

Ceptah Bridge Subtasks mappings

An explanation of the Sub-task Mapping tab is provided below.

Field	Description
Sub-task parent	Tick the option to enable the mapping
Dir	The synchronisation direction. Import: If the imported issue is a sub-task, it will be placed under the task that is linked to its parent issue in JIRA. If the issue is not a sub-task, 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 mapping does not affect issue creation because sub-tasks are created under the issues linked to their parent task even if the sub-tasks mapping is disabled. 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 parent issue in JIRA. If the issue is not a sub-task, 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 difference between the current parent of the linked issue and the issue linked to the parent task in MS Project will be displayed, but the sub-task will not be moved during synchronisation. If it is required to change parent, that needs to be done manually in JIRA.
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.

Field

Description

Sub-task parent

Tick the option to enable the mapping

Dir

The synchronisation direction.

Import: If the imported issue is a sub-task, it will be placed under the task that is linked to its parent issue in JIRA. If the issue is not a sub-task, 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 mapping does not affect issue creation because sub-tasks are created under the issues linked to their parent task even if the sub-tasks mapping is disabled.

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 parent issue in JIRA. If the issue is not a sub-task, 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 difference between the current parent of the linked issue and the issue linked to the parent task in MS Project will be displayed, but the sub-task will not be moved during synchronisation. If it is required to change parent, that needs to be done manually in JIRA.

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.