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 the connector.

Terminology

  • Inbound Direction: From Salesforce to Jira

  • Outbound Direction: From Jira to Salesforce

Symbols

SymbolDirectionNameDescription

<

InboundUnconditionally CompatibleInbound mapping is fully supported.
> OutboundUnconditionally CompatibleOutbound mapping is fully supported.
<? InboundOptional Format-Dependent

If 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.

?>  OutboundOptional Format-DependentIf 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.
<! InboundFormat-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.
!> OutboundFormat-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.
<!! InboundNot RecommendedSome 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.
!!> OutboundNot RecommendedSome 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.
XBothIncompatibleThese field types are not compatible.
<X<InboundUnsupported InboundSome 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

<

>

  <   !>   < !>   < !>   <   !!>   <   !!>   < !>

<

!>

< ?> <!! ?> <!! XXXXX

number

<! >   < > < > <!! !!> <!!  !!> <!! !!>  <!!  !!> <!! !!> X X <!! ?> XXXXXX

date

<!! > <!! !!> <!! !!> X !!> < > XXX !!> X !!> <? ?> <!! ?> XXXXXX

datetime

<!! > XXXXXXXX < > XXXXXXXXXXXXXX

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  < !!>   < !!>   < !>

<

!>

< ?> <!! ?> <!! XXXXX

watches

<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 <! > XXXXXXXXXXXXXX <? ?> <!! ?> XXXXXX
user
<! > XXXXXXXXXX <!! X <!
X <! ?> <!! ?> XXXXXX
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 > XXXXXXXXXXXXXXXXXXXX

timetracking - Σ original estimate

X
> X > X > XXXXXXXXXXXXXXXXXXXX

timetracking - r emaining estimate

X
> X > X > XXXXXXXXXXXXXXXXXXXX

timetracking - Σ r emaining estimate

X
> X > X > XXXXXXXXXXXXXXXXXXXX

timetracking - time spent

X
> X > X > XXXXXXXXXXXXXXXXXXXX

timetracking - Σ time spent

X
> X > X > XXXXXXXXXXXXXXXXXXXX

securitylevel

XXXXXXXXXXXXXXXXXXXXXXXXXX

progress

XXXXXXXXXXXXXXXXXXXXXXXXXX

comments-page

XXXXXXXXXXXXXXXXXXXXXXXXXX
option
<! > XXXXXXXXXXXXXX <? ?> <!! ?> XXXXXX
option-with-childX > XXXXXXXXXXXXXXX ?> X ?> XXXXXX

votes

X

 X

XXXXXXXXXXXXXXXXXXXXXXXX
sd-customerrequesttypeX > XXXXXXXXXXXXXXX ?> XXXXXXXX
versionX > X !!> X !!> X !!> XXXXXXXXX !> X !>
XXXXXX

array<attachment>

<! 

 !>

XXXXXXXXXXXXXXXXXXXXXXXX

array<string>

<!

 !>

XXXXXXXXXXXXXXX X < > XXXXXX

array<worklog>

X 

 X

XXXXXXXXXXXXXXXXXXXXXXXX

array<component>

<! 

 !>

XXXXXXXXXXXXXX X X   < > XXXXXX

array<issuelinks>

<! 

!>

XXXXXXXXXXXXXXXXXXXXXXXX

array<option>

<! 

!>

XXXXXXXXXXXXXX < !!> < > XXXXXX

array<group>

<!

!>

XXXXXXXXXXXXXX < !!> < > XXXXXX

array<version>

<! 

!>

XXXXXXXXXXXXXX < !!> < > XXXXXX