Jira field type to Salesforce field type compatibility

This page outlines which Jira field types are compatible with Salesforce field types in Connector for Salesforce & Jira. When mapping fields between Jira and Salesforce, not every field type pairing works the same way, and some are incompatible. Compatibility depends on the data types involved, the sync direction, and whether the source value matches the format the target field expects.

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
A combination of multiple styles (for example, bold, italics, etc.) on Salesforce does not translate well to Jira Wiki Markup

The Compatibility matrix below shows how each Jira field type maps to each Salesforce field type in both directions (Salesforce → Jira and Jira → Salesforce). Use the legend to quickly assess whether a mapping is fully supported, requires a specific format or value mapping to succeed, or should be avoided altogether. For the most common pairings, such as text, numbers, and dates, see the detailed breakdowns in Common compatible mappings further down the page.

Compatibility symbols

	Unconditionally compatible	Mapping is fully supported.
	Format-sensitive	Mapping is supported only if the field source value is in the expected target format, or you have defined the explicit value mapping. If the format doesn’t match, sync can fail, the target field may be emptied, or left unchanged, depending on the field type. For example, when a Jira string field mapped to a Salesforce picklist field, when the field value (high priority) matches exactly a picklist option (high priority defined in Salesforce), or an explicit value mapping is defined for it.
	Not recommended	Mapping may work with explicit value mapping configured, but fails in most cases. In most cases, a more suitable field type pairing exists in Jira or Salesforce. For example: mapping a Jira number field to a Salesforce date field requires a value mapping and is fragile; a Jira date field is the better choice.
	Incompatible	These field types cannot be mapped. This includes fields that are structurally incompatible, and Jira fields that are read-only (system-managed), which block any mapping from Salesforce to Jira.

Compatibility matrix

Rows are Jira field types and Columns are Salesforce field types. For each Jira field type, there are two rows representing the synchronization direction.

	Direction	boolean	date	datetime	double currency percent	encryptedstring	id reference	int	multipicklist	picklist	string, textarea	Text Area (Rich)	url phone email

	Direction	boolean	date	datetime	double currency percent	encryptedstring	id reference	int	multipicklist	picklist	string, textarea	Text Area (Rich)	url phone email
array←component→	SF → Jira
array←component→	Jira → SF
array←group→	SF → Jira
array←group→	Jira → SF
array←option→	SF → Jira
array←option→	Jira → SF
array←string→	SF → Jira
array←string→	Jira → SF
array←version→	SF → Jira
array←version→	Jira → SF
date	SF → Jira
date	Jira → SF
datetime	SF → Jira
datetime	Jira → SF
issuetype	SF → Jira
issuetype	Jira → SF
number	SF → Jira
number	Jira → SF
option	SF → Jira
option	Jira → SF
option-with-child	SF → Jira