Content Comparison

Overview

This guide illustrates what you can expect  when a Fields Mapping is configured on a mapping.

...

This guide explain in detail all mentioned  topics so that you can configure suitable fields mappings.

Anchor
field-available field-available

Fields availability and allowed Mapping

Fields availability

All JIRA default fields are available for a Fields mapping configuration.

...

Fields mappings around different field’s type

From	To	Allowed
Text Field (single line)	Text Field (multi line)
Text Field (multi line)	Text Field (single line)
Summary, Description, Custom fields	Affect/Fix Versions
Summary, Description, Custom fields	Priority
Summary, Description, Custom fields	Assignee
Priority	Summary, Description, Custom fields
Component	Fix/Affect Versions
Fix/Affect Versions	Component
Fix Versions	Affect Versions
Affect Versions	Fix Versions
Assignee	Reporter
Reporter	Assignee
Component	Summary, Description, Custom fields
Fix/Affect Versions	Summary, Description, Custom fields
Assignee	Summary, Description, Custom fields

Allowable

...

fields  for Sync on create

The sync on create parameter set to True allows to:

...

On issue linking via the Quick actions buttons,  attachments on the target issue are synced on all the source issue and, if other synchronizations have been configured on the source issue, they are propagated again indefinitely.

Anchor
comment comment

Comment’s Syncing behavior

Main difference between Comments syncing and other field syncing consists of it is performed at one linking’s level.

...

• a comment added by the user includes the following header: Comment synced by HQL (id:<Issue id>) 
• a comment added by the system includes the following header: Comment synced by HQL (<Partnership Id>: <Issue id>)

Notice that sync behavior is the same for Partnerships configured across the same or different source and destination Url/s.

...

On issue linking via the Quick actions buttons, all and only the comments added by the user on the linked issue are synced on the source issue.

Anchor
Summary DescriptionCustom fields Summary DescriptionCustom fields

Summary, Description and Custom fields

Sync behavior for the fields Summary, Description, Custom fields, Assignee, Reporter is the same for Partnerships configured across the same or different source and destination Url/s.

...

On linking an existing issue, data are synced from the linked issue to the source issue and, if other synchronizations have been configured on the source issue, syncing is propagated again indefinitely.

Anchor
Component, Affect Version,Fix Version Component, Affect Version,Fix Version

Component, Affect Version and Fix Version syncing behavior

Sync behavior for the fields Component, Affect Version, Fix Version is basically the same behavior described for Summary, Description and Custom fields.

...

Notice that when sync fails as default the add-on set to Null the value of the target field. An exception is made for field configured to be required where the existing value is retained.

Anchor
Priority, Assignee,Reporter Priority, Assignee,Reporter

Priority, Assignee and Reporter syncing behavior

Sync behavior for the fields Priority, Assignee and Reporter is basically the same behavior described for Component, Affect Version and Fix Version, including the behavior on sync failure but

...

• on issue creation and linking via the Quick actions buttons the issue create screen will not be populated by having the values of the source issue
• on issue creation via the Escalate issue post function the issue  will not be populated by having the values of the source issue.

Issue History updates due to synchronization

Updates on issue’s data caused by a synchronization performed by Herzum Quick Linker are retained same way of updates applied by an user.

...