Table of Contents
...
This guide illustrates what you can expect when a Field Mapping is the field synchronization has been configured on a mapping.
As first, consider that not all fields defined on your JIRA instances are available for a Field mapping and synchronization and not all fields mappings mapping, around different fields, are allowed.
After that, consider that depending by the selected field, the syncing behavior can differ for:
...
- Comment
- Attachment
- Summary, Description and Custom fields
- Component, Affect Version and Fix Version
- Priority, Assignee and Reporter.
Furthermore, you must take in consideration that the configured Fields Mappings is notice that synchronization is already active on issue creation as on issue editing, exception made for a few set of fields (Comments, Attachment Assignee and Reporter) on issue creation via the escalate issue post function.
...
Custom fields available for a field mapping syncing configuration are: Text Field (single line), Text Field (multi-line) and the third party custom fields (e.g. the Tempo "Customer Account" custom field) recognized to be text type.
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.
...