Skip to end of banner
Go to start of banner

Jira Field Type to Salesforce Field Type compatibility

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »


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

  • (warning) A combination of multiple styles (e.g. bold, italics, etc.) on Salesforce does not translate well to Jira Wiki Markup
Symbols
SymbolDirectionNameDescription

<

InboundUnconditionally CompatibleInbound mapping is fully supported.
> OutboundUnconditionally CompatibleOutbound mapping is fully supported.
<? InboundOptional 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.

?>  OutboundOptional Format-DependentIf 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.
<! 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. For a better view of the table, you can view this in Compatibility Matrix (full view).



string
 textarea

int



double
 currency
 percent

boolean


date


datetime


url
 phone
 email



id
 reference

picklist

multipicklist

encryptedstring

 location   address

string

<?

?>

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

<

!>

< ?> <!! ?> <!! XXXXX
string textarea<??><!> <!> <!><!!> <!!><!><!><?><!!?><!!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

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 <! > 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-child<! > XXXXXXXXXXXXXX<? ?> <!! ?> XXXXXX

votes

X

 X

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

array<attachment>

XXXXXXXXXXXXXXXXXXXXXXXXXX

array<string>

<!

>

XXXXXXXXXXXXXXX X <! !> XXXXXX

array<worklog>

 X 

 X

XXXXXXXXXXXXXXXXXXXXXXXX

array<component>

<!

>

XXXXXXXXXXXXXX X X   <! !> XXXXXX

array<issuelinks>

X

X

XXXXXXXXXXXXXXXXXXXXXXXX

array<option>

<!

>

XXXXXXXXXXXXXX<! X <! !>XXXXXX

array<group>

<!

>

XXXXXXXXXXXXXX<! !!> <!!>XXXXXX

array<version>

<!

>

XXXXXXXXXXXXXXXX<!!>XXXXXX

array<sd-customerorganization>

X

X

XXXXXXXXXXXXXXXXXXXXXXXX


  • No labels
Error formatting macro: appfire-confluence-analytics: java.lang.NullPointerException: Cannot invoke "com.atlassian.confluence.xhtml.api.MacroDefinition.getMacroId()" because "macroDefinition" is null