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 |
|
...
- 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 via the Quick actions buttons, data are synced from the created issues to the source and, if other synchronizations have been configured on the source issue, syncing is propagated again indefinitely.
On issue creation via the Escalate issue post function, data are synced from the source issue to the target when Sync on create is set to true, syncing is not active on issue creation if Sync on create is set to false.
On linking an existing issue, data are synced from the linked issues to the source and, if other synchronizations have been configured on the source issue, syncing is propagated again indefinitely.
Syncing is source versus target
On issue creation via the Quick actions buttons, data are synced from the source issue to the created issue.
On issue creation via the Escalate issue post function, data are synced from the source issue to the target when Sync on create is set to true, syncing is not active on issue creation if Sync on create is set to false.
On linking an existing issue, data are synced from the source issue to the created issue and, if other synchronizations have been configured on the linked issue, syncing is propagated again indefinitely.
...
On issue creation via the Quick actions buttons, data are synced from the created issue to the source issue.
On issue creation via the Escalate issue post function, data are not synced.
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
| Component, Affect Version,Fix Version | |
| Component, Affect Version,Fix Version |
...
The only difference differing those specific fields from the other type of synchronization is that sync can fail due to different Versions and Components settings across different projects and/or JIRA instance.
When sync fails due to the mentioned scenario, Comments are logged to alert the user for syncing failure. See HQL - General troubleshooting guidelines for further information on this topic.
...