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 |
...
The mentioned setting is available for mostly of the listed fields available for a field mapping, the only fields not still allowed to have this setting are Attachment Assignee and Reporter.
Anchor attachment attachment
Attachment’s Syncing behavior
attachment | |
attachment |
As first you must be aware that attachment synchronization is based on the attachment file name. So, two files having the same name are considered to be the same.
...
- 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.
...