Secondary mappings

Select the default Components.

Import: Has no effect.

Sync (unlinked task): The Components will be used by default when a new issue is created.

Sync (linked task): See the help for the “Field” combo box.

Separate multiple components with the separator defined in the Windows regional settings (“,” for the English locales).

Select the task field to map to issue Components.

Import: The selected task field will be populated with the source issue Components value.

Sync (unlinked task): If the selected task field is not blank, the Components field of the new issue will be populated with the field value. Otherwise, the default Components will be used.

Sync (linked task): If the synchronisation direction is from JIRA to MS Project, the selected task field will be set to the linked issue Components value if it is different from the default Components.

If the synchronisation direction is from MS Project to JIRA and the selected task field is not blank, the issue Components will be set to the field value. If the field is empty, the default Components will be used.

Separate multiple components with the separator defined in the Windows regional settings (“,” for the English locales).

Select the default Affects Versions.

Import: Has no effect.

Sync (unlinked task): The Affects Versions will be used by default when a new issue is created.

Sync (linked task): See the help for the “Field” combo box.

Separate multiple versions with the separator defined in the Windows regional settings (“,” for the English locales).

Select the task field to map to issue Affects Versions.

Import: The selected task field will be populated with the source issue Affects Versions value.

Sync (unlinked task): If the selected task field is not blank, the Affects Versions field of the new issue will be populated with the field value. Otherwise, the default Affects Versions will be used.

Sync (linked task): If the synchronisation direction is from JIRA to MS Project, the selected task field will be set to the linked issue Affects Versions value if it is different from the default Affects Versions.

If the synchronisation direction is from MS Project to JIRA and the selected task field is not blank, the issue Affects Versions will be set to the field value. If the field is empty, the default Affects Versions will be used.

Separate multiple versions with the separator defined in the Windows regional settings (“,” for the English locales).

Select the default Fix Versions.

Import: Has no effect.

Sync (unlinked task): The Fix Versions will be used by default when a new issue is created.

Sync (linked task): See the help for the “Field” combo box.

Separate multiple versions with the separator defined in the Windows regional settings (“,” for the English locales).

Select the task field to map to issue Fix Versions.

Import: The selected task field will be populated with the source issue Fix Versions value.

Sync (unlinked task): If the selected task field is not blank, the Fix Versions field of the new issue will be populated with the field value. Otherwise, the default Fix Versions will be used.

Sync (linked task): If the synchronisation direction is from JIRA to MS Project, the selected task field will be set to the linked issue Fix Versions value if it is different from the default Fix Versions.

If the synchronisation direction is from MS Project to JIRA and the selected task field is not blank, the issue Fix Versions will be set to the field value. If the field is empty, the default Fix Versions will be used.

Separate multiple versions with the separator defined in the Windows regional settings (“,” for the English locales).

Select the task field to map to the description of the Fix Version.

Import: The selected task field will be populated with the description of the Fix Version assigned to the source issue. There must be only one version.

Sync (unlinked task): Has no effect.

Sync (linked task): The selected task field will be set to the description of the version assigned to the linked issue.

Select the task field to map to the released flag of the Fix Version.

Import: The selected task field will be populated with the released flag of the Fix Version assigned to the source issue. There must be only one version.

Sync (unlinked task): Has no effect.

Sync (linked task): The selected task field will be set to the released flag of the version assigned to the linked issue.

Select the task field to map to the start date of the Fix Version.

Import: The selected task field will be populated with the start date of the Fix Version assigned to the source issue. There must be only one version.

Sync (unlinked task): Has no effect.

Sync (linked task): The selected task field will be set to the start date of the version assigned to the linked issue.

Select the task field to map to the release date of the Fix Version.

Import: The selected task field will be populated with the release date of the Fix Version assigned to the source issue. There must be only one version.

Sync (unlinked task): Has no effect.

Sync (linked task): The selected task field will be set to the release date of the version assigned to the linked issue.

Select the task field to map to issue Description.

Import: The selected task field will be populated with the source issue Description value.

Sync (unlinked task): The Description field of the new issue will be populated with the value of the selected task field.

Sync (linked task): If the synchronisation direction is from JIRA to MS Project, the selected task field will be set to the linked issue Description value.

If the synchronisation direction is from MS Project to JIRA, the issue Description will be set to the value of the selected task field.

Select the task field to map to issue Environment.

Import: The selected task field will be populated with the source issue Environment value.

Sync (unlinked task): The Environment field of the new issue will be populated with the value of the selected task field.

Sync (linked task): If the synchronisation direction is from JIRA to MS Project, the selected task field will be set to the linked issue Environment value.

If the synchronisation direction is from MS Project to JIRA, the issue Environment will be set to the value of the selected task field.

Select the task field to map to issue Votes.

Import: The selected task field will be populated with the source issue Votes value.

Sync (unlinked task): Has no effect.

Sync (linked task): The selected task field will be set to the issue Votes value.

Select the task field to map to issue Labels.

Import: The selected task field will be populated with the source issue Labels value.

Sync (unlinked task): If the synchronisation direction is from JIRA to MS Project, the selected task field will be set to the linked issue Labels value. If the synchronisation direction is from MS Project to JIRA, the issue Labels will be set to the value of the selected task field.

Sync (linked task): The selected task field will be set to the issue Labels value.

Separate multiple labels with the separator defined in the Windows regional settings (“,” for the English locales).

Please note that Labels are supported only for JIRA 4.0 and higher.

Select the task field to map to issue Created.

Import: The selected task field will be populated with the source issue Created value.

Sync (unlinked task): Has no effect.

Sync (linked task): The selected task field will be set to the issue Created value.

Select the task field to map to issue Updated.

Import: The selected task field will be populated with the source issue Updated value.

Sync (unlinked task): Has no effect.

Sync (linked task): The selected task field will be set to the issue Updated value.

Tick the option to enable Comments synchronisation. Comments will be copied to the Notes field. This is the only field in MS Project that can accomodate a large block of text.

Import: The Notes field will be populated with the comments for the source issue.

Sync (unlinked task): Has no effect.

Sync (linked task): The Notes field will be set to the issue comments.

Select the task field to map to issue Watchers. The value of the field is a list of user names (logins) delimited with the separator defind for the current Windows profile culture, e.g. comma for the English locale.

Import: The selected task field will be populated with the list of the users watching the source issue.

Sync (unlinked task):The Watchers of the new issue will be adjusted to match the value of the selected task field.

Sync (linked task): If the synchronisation direction is from JIRA to MS Project, the selected task field will be set to the list of the users watching the linked issue.

If the synchronisation direction is from MS Project to JIRA, the Watchers of the linked issue will be adjusted to match the value of the selected task field.

Tick the option to enable Hyperlink population.

Import: The task Hyperlink field will be populated with the link to the source issue in JIRA.

Sync (unlinked task): The task Hyperlink field will be populated with the link to the new issue in JIRA.

Sync (linked task): The selected task field will be set to the link to the issue in JIRA.