Table of Contents
...
This guide explain in detail all mentioned topics so that you can configure suitable fields mappings.
Anchor field-available field-available
| field-available | |
| field-available |
...
Fields availability and Fields mapping around different field’s type
Fields availability
All JIRA default fields are available for a Fields mapping configuration.
Custom fields available for a field 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
...
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 |
|
...
- 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.
...
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.
...