Jira field type to Salesforce field type compatibility
This page outlines which Jira field types are compatible with Salesforce field types in the latest version of Connector for Salesforce & Jira.
Synchronization direction
Field mapping compatibility depends not only on the Jira and Salesforce field types but also on the synchronization direction. Some fields are compatible for synchronization from Jira to Salesforce, but are incompatible in the opposite direction from Salesforce to Jira.
Mappings below apply to both standard and custom Jira and Salesforce field types
You can get Jira string type compatibility with Salesforce string textarea starting release versions 2.36.17 of Connector for Salesforce and Jira.
If you added the mappings for rich content fields before versions 2.36.17, please re-do the configuration for this feature to work
A combination of multiple styles (for example, bold, italics, etc.) on Salesforce does not translate well to Jira Wiki Markup
Compatibility symbols
Symbol | Direction | Name | Description |
|---|---|---|---|
← | From Salesforce to Jira | Unconditionally Compatible | From Salesforce to Jira mapping is fully supported. |
→ | From Jira to Salesforce | Unconditionally Compatible | From Jira to Salesforce mapping is fully supported. |
←? | From Salesforce to Jira | Optional Format-Dependent | If the Salesforce value is in the expected Jira format or a value mapping exists, converting it to the desired value/format in Jira sync will work as expected. Otherwise depending on the target field, either an empty value will be used (emptying the target field) or the sync does not affect the target field. |
?→ | From Jira to Salesforce | Optional Format-Dependent | If the Jira value is in the expected Salesforce format or a value mapping exists, converting it to the desired value/format in Salesforce sync will work as expected. Otherwise depending on the target field, either an empty value will be used (emptying the target field) or the sync does not affect the target field. |
←! | From Salesforce to Jira | Format-Sensitive | From Salesforce to Jira mapping is supported, sync works only if the Salesforce value is in the expected Jira format or a value mapping exists, converting it to the desired value/format in Jira, otherwise sync will fail. |
!→ | From Jira to Salesforce | Format-Sensitive | From Jira to Salesforce mapping is supported, sync works only if the Jira value is in the expected Salesforce format or a value mapping exists, converting it to the desired value/format in Salesforce, otherwise sync will fail. |
←!! | From Salesforce to Jira | Not Recommended | Some types might be compatible with value mapping but a mapping between them is not recommended as it fails most of the time. In most cases you can find more suitable field types in Jira or Salesforce to map to your desired field. |
!!→ | From Jira to Salesforce | Not Recommended | Some types might be compatible with value mapping but a mapping between them is not recommended as it fails most of the time. In most cases you can find more suitable field types in Jira or Salesforce to map to your desired field. |
X | Both | Incompatible | These field types are not compatible. |
←X | From Salesforce to Jira | Unsupported From Salesforce to Jira | Some fields in Jira are read-only, hence an From Salesforce to Jira mapping for them is not supported. |
Compatibility Matrix
Rows are Jira field types and Columns are Salesforce field types.
You can use filters from the head row to select Jira fields and compatible fields.
Need support? Create a request with our support team.