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.
...
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.
Issue History Logs
Syncing of Updates on issue’s data caused by a synchronization performed by Herzum Quick Linker are retained same way of user’s updates applied by an user.
Notice that the applied changes updates are attributed to the user configured on the partnership as source/destination credential:
...