Table of Contents
...
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 |
...
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.
Anchorcomment comment
Comment’s Syncing behavior
comment | |
comment |
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 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.
...