Fields Compatibility Matrix
Supported fields (IssueSYNC Server)
Field | Map to same field | Map to other fields |
|---|---|---|
| Summary |  (required) | Text Field |
| Description | | Text Field |
| Due date | | Text Field |
| Labels | |
|
| Priority | By name | Text Field |
| Assignee | Based on username | Text Field |
| Reporter | Based on username | Text Field |
| Comments | Handled by Contract | - |
| Service Desk's Internal Comments | Handled by Contract (since v1.6) | - |
| Service Desk's Shared Comments | Handled by Contract (since v1.6) | - |
| Attachments | Handled by Contract | - |
| Version | By name (with create) | Text Field |
| Component | By name (with create) | Text Field |
| Resolution | - | |
| Worklogs |
* synchronization only with JIRA Server ↔ JIRA Server | |
| Status | It is made via Workflow Synchronization | Text Field |
Issue Key | It happens out-of-the-box. Can be activated using Synchronized Issues View Please, don't setup this in Field Mapping, it is available via this issue panel. | Text Field |
| Issue Type | It works by contract definition | Text Field |
Created Date, Updated Date, Resolved Date | These built-in fields are controlled by JIRA. Their values can be map only on some other custom fields. |
Custom Date Field Type |
| Request Type |
* you should avoid changing the request type - Atlassian recommendation | Text Field |
| Request Participants | Based on username (since v1.6) | Text Field |
| Custom Text Field Type | | |
| Custom Number Field Type | | Text Field |
| Custom Labels Field Type | |
|
| Custom Select List Field Type | By value's name | Text Field |
| Custom Multi Select List Field Type | since v1.5 | Text Field |
| Custom Cascading Field Type | since v2.0 | Text Field |
| Custom Checkbox Field Type | By name | Text Field |
| Custom Radio Button Field Type | By name | Text Field |
| Custom Date Field Type | | Text Field |
| Custom MultiGroup Picker |  We are working on it | |
| Custom User Picker | We are working on it |
 Assignee and Reporter fields won't be updated in remote JIRA instance if no user will be found. |