Skip to end of banner
Go to start of banner

Supported Fields for Mapping

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 8 Next »

Introduction

This page provides information regarding the supported fields for mapping.

Contents

Jira

Most common Salesforce objects are supported, such as:

  • Case
  • Account
  • Contact
  • Opportunity
  • Lead
  • Task
  • User

In fact, the Salesforce & Jira Server Connector supports almost all standard field and custom field types, except for Cascading Select List.

Custom fields that are bundled with other add-ons are not supported, including add-ons that are developed by Atlassian.

All supported fields will be available in the Jira Field pull-down menu in the Configure Mapping screen.

Salesforce

Similar to Jira, the Connector only supports standard field and custom field types. No third party custom fields are supported. All supported fields will be available in the Remote Field pull-down menu in the Configure Mapping screen.

Page Contents

Suggestions for Field Mapping Pairing Based on Field Types

Jira FieldSalesforce FieldNote
Component/s (Standard field - Select List (multiple choices))Picklist (Multi-Select)Will work if using a single Picklist but will cause an error if you choose more than one option in Jira
Affects Version/s  (Standard field - Select List (multiple choices))Picklist (Multi-Select)Will work if using a single Picklist but will cause an error if you choose more than one option in Jira
Fix Version/s  (Standard field - Select List (multiple choices))Picklist (Multi-Select)Will work if using a single Picklist but will cause an error if you choose more than one option in Jira
Select List (single choice)Single Picklist 
Select List (multiple choices)Picklist (Multi-Select) 
Date PickerDate 
Date Time PickerDate/Time 
URL FieldURL 
TextTextIncludes a multi-line text field

Remote Object Link

Lookup RelationshipThis is a connector custom field. It should be mapped with an Object Id in the Remote Field pull-down menu

These suggestions are for bi-directional synchronization.

If using only single direction synchronization, you can map with any field type such as "Text".

  • No labels