Table of Contents
...
Fields mapping 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 |
...
Depending by the configured sync versus you can expect the syncing behavior described bellowbelow.
Syncing is Both
On adding one or more attachments, they are synced on all the linked issue/s and, if other synchronizations have been configured on the target issue/s, they are propagated again indefinitely.
...
- 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.
Depending by the configured sync versus you can expect the syncing behavior described bellowbelow.
Syncing is Both
On adding a comment, it's synced on all the linked issue/s.
...
Depending by the configured sync versus you can expect the syncing behavior described bellowbelow.
Syncing is Both
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.
...