Issue link mappings

To change the issue link mappings, select Links tab in the Project settings window.

Issue Link Mappings tab

An explanation of the Links Mappings tab is provided below.

Field	Description
Links table	Contains link mappings
JIRA	The name of the mapped link
Dir	The synchronisation direction
Microsoft Project	The mapped Microsoft project field description
Issue Types	The issue types the mapping is applied to
X (cross)	Deletes the mapping
Details pane	Shows the details of the selected mapping
Link type	Select the JIRA issue link type to be mapped.
Link	Tick either the inward or outward links to be mapped.
Direction Button	Press to change the synchronisation direction.
Predecessors	Tick the option to map the issue links to the Predecessors field in MS Project. Import: Dependencies on the tasks that match the issues linked to the imported issue will be added to the imported task. Sync (unlinked task): Links to the issues matching the predecessors of the published task will be added to the new issue. Sync (linked task): If the direction is from JIRA to MS Project, dependencies on the tasks that match the issues linked to the synchronised issue will be set for the synchronised task. If the direction is from MS Project to JIRA, links to the issues matching the predecessors of the synchronised task will be added to the synchronised issue and any redundant links will be removed.
SF/SS/FS/FF	Select the dependency type that will be used for linking to predecessors. The options include Start-to-Finish (SF), Start-to-Start (SS), Finish-to-Start (FS) and Finish-to-Finish (FF)
Remove other types	If the direction is from JIRA to MS Project, tick the option to delete all existing predecessors where the dependency type is different from the type selected in the SF/SS/FS/FF field. That is, when this switch is on, the mapping controls all predecessors for a task. If the option is off, predecessors of other types are unaffected by the mapping. If a link mapping has the switch on, it must be the only predecessor mapping defined.
Field	Tick the option to map the issue links to a custom text field that contains a list of issue keys. Import: The selected field will be populated with the keys of the issues linked to the imported issue. Sync (unlinked task): Links to the issues with the keys from the selected text field will be added to the new issue. Sync (linked task): If the direction is from JIRA to MS Project, the selected field will be populated with the keys of the issues linked to the synchronised issue. If the direction is from MS Project to JIRA, links to the issues with the keys from the selected text field will be added to the synchronised issue and any redundant links will be removed.
Field (Combo Box)	Select the field to map to issue links.
Parent	Tick the option to map the issue link to the parent (summary) task. Import: The new task will be added as the last child of the task that match the issue linked to the synchronised issue. Sync (unlinked task): A link to the issue matching the parent task will be added to the new issue. Sync (linked task): If the direction is from JIRA to MS Project, the synchronised task will be moved under the task that match the issue linked to the synchronised issue. If the direction is from MS Project to JIRA, a link to the issue matching the parent task will be added to the synchronised issue and any redundant links will be removed.
Ancestor of type	Tick the option to map the issue 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): A link to the issue matching the first summary task up in the hierarchy whose assigned JIRA issue type satisfies the filter condition will be added to the new issue. Sync (linked task):The direction from JIRA to MS Project is not supported. If the direction is from MS Project to JIRA, a link to the issue matching the first summary task up in the hierarchy whose assigned JIRA issue type satisfies the filter condition will be added to the synchronised issue and any redundant links will be removed.
Ancestor on level	Tick the option to map the issue 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):A link to the issue matching the summary task on the selected level up in the hierarchy will be added to the new issue. Sync (linked task):The direction from JIRA to MS Project is not supported. If the direction is from MS Project to JIRA, a link to the issue matching the summary task on the selected level up in the hierarchy will be added to the synchronised issue and any redundant links will be removed.
Task Outline Level	Defines the level range the mapping is applied to. This is the level of the synchronised task and not the one of its parent. The option is regarded only when data is copied from MS Project to JIRA during synchronisation and ignored during import or when the synchronisation direction is from JIRA to MS Project.
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.
Add	Adds a new mapping for a link type.