Configure entity, field and value mappings

This page helps you configure entity mappings, field, and value mappings for your bindings.

Configure entity mappings to set up Jira issue types to match the corresponding Salesforce objects.
Configure field mappings to set up Jira fields to match the corresponding Salesforce fields.
Set up value-to-value mapping for each field mapping and define what should be done in cases not covered by the mappings.

If you haven't done so, consult the Bind a project to a connection page before reading this page.

To find out what Jira field types are compatible with Salesforce field types, visit the Jira Field Type to Salesforce Field Type compatibility page.

On this page: 1 Step 1: Configure entity mappings 2 Step 2: Configure field mappings 3 Step 3: Set default value 4 Step 4: Configuring value mappings 5 Creating inbound-only or outbound-only mappings 6 Related information

On this page: 1 Step 1: Configure entity mappings 2 Step 2: Configure field mappings 3 Step 3: Set default value 4 Step 4: Configuring value mappings 5 Creating inbound-only or outbound-only mappings 6 Related information

https://appfire.wistia.com/medias/6e5iwgqduh

Step 1: Configure entity mappings

Go to Settings > Apps. In the sidebar, under Connector for Salesforce, select Bindings.
On the Bindings screen, choose the binding to configure and click Mapping.

On the Mapping Configure screen, click +Add Entity Mapping.
(Alternatively, if you have a previously exported entity mapping, you can also Import it here.)

The Add Entity Mapping window appears.

Choose the Issue Type you want mapped to specific Salesforce objects.
Click Add.

Step 2: Configure field mappings

On the Mapping Configure screen, click Mappings for the entity you created.

The Story to Case field mapping window appears.
Choose the Jira Fields that match the corresponding Salesforce Field.
You can customize the Sync Direction (inbound or outbound) by clicking the Green Arrow buttons.
The example below matches the Summary Jira Issue Field to the Subject Salesforce Field and the Description Jira Issue Field to the Description Salesforce Field:
4. Click Add and Save.

Step 3: Set default value

Before synchronizing data between Jira and Salesforce, decide how to handle field values not covered by the mapping. Setting default values and actions lets you choose whether you want to copy the original value, force a custom value, leave it empty (if allowed), or raise an error to ensure all field values are synchronized according to your needs. Choose one of the following options:

Copy value - SFJC copies and uses the original field value from the source to the destination system. (This is the default option.)
For example, if you want Jira issue status to match their equivalents in Salesforce, this option ensures that a Jira issue with In Progress satus is set to In Progress in Salesforce.
Set value - SFJC assigns a predefined value of your choice for the field.
For example, if you want all Jira issues to have UI as their component in Salesforce, regardless of their original component, you can set UI as a default component in Salesforce. This ensures consistent categorization of Jira issues in Salesforce, aligning with your business requirements.
Set empty - SFJC sets the field value to empty. This option is not available for required fields that need to have their value set.
Raise error -SFJC raises an error, and synchronization fails.

When creating a Jira issue from Salesforce, field values are filled based on the mapping or default values you’ve set. However, there’s one exception—Priority.

Jira doesn’t allow the Priority field to be empty, so it always has a default value set. If the Priority field is empty in Salesforce, the value is populated with the Jira default priority instead of the one set in the Connector for Salesforce & Jira. The correct Priority value, as configured in the Connector, will only synchronize after pushing from Salesforce.

To define default values:

Click Configure next to the selected Jira and Salesforce Field mapping.
Select a Jira default and Salesforce default value:
- Copy value
- Set value (requires entering your preferred value)
- Set empty
- Raise error
Click Save.

Step 4: Configuring value mappings

Additionally, you can define specific value mapping to match Jira and Salesforce field values. For example:

Mapping the Jira status In Progress with Salesforce Status Escalated to Dev.
Mapping the Jira priority Major with Salesforce priority High.
Mapping the Jira component UI with Salesforce Case Reason User Interface.

If the value is not mapped, SFJC continues according to the defined default values.

To map field values:

From Step 2, select the Sync direction (inbound or outbound) desired for the field mapping.
Click Configure.
Under Configure values, enter the values for Jira and Salesforce accordingly.
If the value of the Jira field is the User type, then you can select available Jira users from the dropdown list.
Click Add and Save.

Creating inbound-only or outbound-only mappings

You can configure separate value mappings for each direction (inbound or outbound). This also allows you to map values in a one-to-many relationship. Create two records for the same field, one for each direction, and then proceed with configuring the value mappings.

For example:

Map Components Jira field to Case Reason Salesforce field separately for each direction (inbound or outbound).
For inbound-only mapping, map, for example, UI Jira task value with the User Interface Case Reason Salesforce value.
For outbound-only mapping, map, for example, Installation Jira task value with the Packaging Case Reason Salesforce value.