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.

Terminology

Inbound Direction: From Salesforce to Jira
Outbound Direction: From Jira to Salesforce

Mappings below apply to both standard and custom Jira and Salesforce field types
You can get Salesforce HTML formatted fields translated to Jira text area fields 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 (e.g. bold, italics, etc.) on Salesforce does not translate well to Jira Wiki Markup

Symbols

Symbol	Direction	Name	Description

Symbol	Direction	Name	Description
<	Inbound	Unconditionally Compatible	Inbound mapping is fully supported.
>	Outbound	Unconditionally Compatible	Outbound mapping is fully supported.
<?	Inbound	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.
?>	Outbound	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.
<!	Inbound	Format-Sensitive	Inbound 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.
!>	Outbound	Format-Sensitive	Outbound 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.
<!!	Inbound	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.
!!>	Outbound	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<	Inbound	Unsupported Inbound	Some fields in Jira are read-only, hence an inbound mapping for them is not supported.

Compatibility Matrix

Rows are Jira field types and Columns are Salesforce field types.

	string textarea		int		double currency percent		boolean		date		datetime		url phone email		id reference		picklist		multipicklist		encryptedstring		location		address

	string textarea		int		double currency percent		boolean		date		datetime		url phone email		id reference		picklist		multipicklist		encryptedstring		location		address
string	<?	?>	<	!>	<	!>	<	!>	<	!!>	<	!!>	<	!>	<	!>	<	?>	<!!	?>	<!!	X	X	X	X	X
string textarea	<?	?>	<	!>	<	!>	<	!>	<	!!>	<	!!>	<	!>	<	!>	<	?>	<!!	?>	<!!	X	X	X	X	X
number	<!	>	<	>	<	>	<!!	!!>	<!!	!!>	<!!	!!>	<!!	!!>	<!!	!!>	X	X	<!!	?>	X	X	X	X	X	X
date	<!!	>	<!!	!!>	<!!	!!>	X	!!>	<	>	X	X	X	!!>	X	!!>	<?	?>	<!!	?>	X	X	X	X	X	X
datetime	<!!	>	X	X	X	X	X	X	X	X	<	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X
issuetype	<X<	>	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	?>	<X<	?>	<X<	X	<X<	X	<X<	X
project	<X<	>	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	?>	<X<	?>	<X<	X	<X<	X	<X<	X
resolution	<	>	<	X	<	X	<	X	<	!!>	<	!!>	<	!>	<	!>	<	?>	<!!	?>	<!!	X	X	X	X	X
watchers	<X<	X	<X<	>	<X<	>	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X
priority	<!	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	<?	?>	<!!	?>	X	X	X	X	X	X
user	<!	>	X	X	X	X	X	X	X	X	X	X	<!!	X	<!	X	<!	?>	<!!	?>	X	X	X	X	X	X
status	<X<	>	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	X	<X<	?>	<X<	?>	<X<	X	<X<	X	<X<	X
timetracking - original estimate	X	>	X	>	X	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
timetracking - Σ original estimate	X	>	X	>	X	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
timetracking - r emaining estimate	X	>	X	>	X	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
timetracking - Σ r emaining estimate	X	>	X	>	X	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
timetracking - time spent	X	>	X	>	X	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
timetracking - Σ time spent	X	>	X	>	X	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
securitylevel	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
progress	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
comments-page	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
option	<!	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	<?	?>	<!!	?>	X	X	X	X	X	X
option-with-child	<!	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	<?	?>	<!!	?>	X	X	X	X	X	X
votes	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
sd-customerrequesttype	X	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	?>	X	X	X	X	X	X	X	X
version	X	>	X	!!>	X	!!>	X	!!>	X	X	X	X	X	X	X	X	X	!>	X	!>	X	X	X	X	X	X
array<attachment>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
array<string>	<!	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	<!	!>	X	X	X	X	X	X
array<worklog>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
array<component>	<!	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	<!	!>	X	X	X	X	X	X
array<issuelinks>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X
array<option>	<!	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	<!	X	<!	!>	X	X	X	X	X	X
array<group>	<!	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	<!	!!>	<!	!>	X	X	X	X	X	X
array<version>	<!	>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	<!	!>	X	X	X	X	X	X
array<sd-customerorganization>	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X	X