Contents

Jira and Salesforce Integration: Step-by-Step Data Sync guide

The Jira Salesforce Data Sync plugin allows you to sync Jira and Jira Service Management issue fields to Salesforce CRM object-like cases. This guide demonstrates how to sync Jira and Jira Service Management issue fields to the Salesforce Case object.

1. Configure Salesforce App

To configure the Salesforce app please make sure that you have System Administrator access to your Salesforce instance in order to complete this step and connect your Jira and Jira Service Management to Salesforce.

Automatic Connection
Manual Connection

It can also be called the One-Click Authorization mechanism. In this method of authorization, you don't need client credentials (like Consumer Key or Consumer Secret) to connect to Salesforce.

Note: In order to use this method of connection to connect to Salesforce, you need to make sure that https://connect.xecurify.com:443 is whitelisted for your datacenter instance. Alternatively, you can use the Manual Connection method to connect to Salesforce.

First select your Salesforce Environment as Production.
Now, click on the Save Configuration button to save your environment.

Auto Connect - Integrate Jira Salesforce Data Sync

Click on the Connect to Salesforce button.
You will be prompted to enter your Salesforce credentials once entered you will be asked for certain permissions, these permissions are:
- Access the identity URL Service.
- Manage user data via APIs.
- Perform requests at any time.
Please click on the Allow button to connect to Salesforce.

Salesforce Connect - Integrate Jira Salesforce Data Sync

After clicking Allow, you will successfully connect to Salesforce. You will see the following screen confirming your connection to Salesforce.

Connection Successful - Integrate Jira Salesforce Data Sync

Follow the steps below to connect to Salesforce using a manual/custom app:

To connect your Jira instance to Salesforce using the manual connection, you will need to create a connected app in Salesforce.

Go to the Salesforce login page and login as an Administrator.
You will be represented with the home screen of Salesforce.
Navigate to the Setup tab.

Manual Connect - Integrate Jira Salesforce Data Sync

Under the PLATFORM TOOLS section, navigate to the Apps in the left menu.
Select the App Manager option.

In the same window, head to the top right corner and click on New Connected App button to create a new application.

Fill the required information in below boxes.
Under the API (Enable OAuth Settings), check the option of Enable OAuth settings.

Connected App Name	Enter the name as 'TestJiraSync'.
API Name	By default, it just copies the Connected App Name.
Contact Email	Enter any email of your choice.
Available OAuth Scopes	Select Manage user data via APIs (api) and Perform requests on your behalf at any time (refresh_token, offline_access) options.

For the callback URL, you can navigate to the plugin’s Connect To Salesforce tab and copy the Redirect URI as shown below:

Plugin Manual Connect - Integrate Jira Salesforce Data Sync

Then paste the copied URL under the Callback URLoption.

Then, click on Save.
Now the user will be prompted with the confirmation page, click on Continue and move on the next page.

Once this is done the user will be able to view the app they have configured, then click on Manage Consumer Details button to get Consumer Key and Consumer Secret.

You might get a 2FA prompt depending on the login policies, enter the OTP or 2FA prompt if asked, to get Consumer Key and Consumer Secret which are necessary to enable a connection between Salesforce and WordPress.

Note: As Salesforce takes around 20-25 minutes to validate the newly created connected app on its end therefore you need to wait for 20-25 minutes before trying to use the Consumer Key and Consumer Secret to connect your Jira/Jira Service Management instance to salesforce with your newly created connected app. Also if you make changes to your connected app in Salesforce, it does take around 20-25 minutes to validate and reflect those changes.

Navigate to the Jira Salesforce Data Sync plugin.

Under the tab Connect To Salesforce, paste the Consumer Key and Consumer Secret from the Salesforce App.

Select Environment	Select Production as your Salesforce environment.
Client ID	Paste the Consumer Key from the Salesforce App.
Client Secret	Paste the Consumer Secret from the Salesforce App.

Click on Save Configuration.
Click on the Connect to Salesforce button. You will be prompted to enter your salesforce credentials, once entered, you will be asked for certain permissions, please click on Allow to connect to Salesforce.

Connectional Successful - Integrate Jira Salesforce Data Sync

2. Issue Mapping

Under the Configure Issue Mapping tab, you can click on the Add Project button to map an issue type of a project with a Salesforce object Case.

Issue Mapping - Integrate Jira Salesforce Data Sync

Select the Jira project from the Jira project dropdown and click on Next.

Select Project - Integrate Jira Salesforce Data Sync

Click on the Add Issue Mapping button to map an issue type of the selected project and with a Salesforce object.
Select the issue type from the Jira Project Issue Type dropdown and then select Case from the Salesforce Object dropdown and click on Save.

Map Salesforce Object - Integrate Jira Salesforce Data Sync

Now we will be mapping the fields of the salesforce Case object with the fields of the selected issue type in the Map Issue fields to Salesforce fields section.
Search for Name from the Add New Salesforce Field dropdown, select it, and click on Add Salesforce Field button to add a new mapping record.
You can click the Add Salesforce Field button to add a new mapping record. This will populate the Salesforce SuppliedName field.

Jira Salesforce Field Mapping - Integrate Jira Salesforce Data Sync

Now map the Salesforce SuppliedName field to the Jira/Jira Service Management to Summary field. You can select the Summary field from the Select Field dropdown.

Note: While creating an issue of the mapped issue type under the selected project please make sure that the length of the summary field is less than 80 characters as it is mapped to the salesforce SuppliedName field and it accepts values that have characters less than 80. If the length of the value present in the summary field is greater than 80 then the record will be rejected by Salesforce.

Finally, you can click the Save Object Mapping button available in this section to save the entire mapping.

Jira Salesforce Flow - Integrate Jira Salesforce Data Sync

The above diagram explains various sections of a block of field map in detail.
Now whenever a ticket is created/updated for the mapped issue type of the selected Jira project the summary field of the issue will be synced to the Salesforce Case object as the summary field is mapped in the plugin.
If you want to map other issue fields with other fields of your salesforce object, then you need to create a map between them as well. You can add additional fields for mapping using the Add New Salesforce Field dropdown.

Points to Remember

While creating the mapping please make sure to map all the required fields of the Salesforce object because if data is not synced to the required fields of a Salesforce object then the Salesforce doesn’t create a record.
While creating a mapping please make sure that the data type of the mapped Salesforce and Jira fields are the same. For example: a boolean field cannot be mapped to a picklist field. Also while mapping a Jira/JSM field with a picklist-type field of Salesforce please make sure that the Jira field only contains the values valid of the mapped Salesforce picklist field.
Please make sure that you map a Salesforce reference type field to a Jira/Jira Service Management field which contains an 18-digit Salesforce record ID. If you map a Salesforce reference type field to a Jira/Jira Service Management field that does not contain an 18-digit Salesforce record ID then Salesforce will reject the record it means the issue fields from Jira/Jira Service Management will not be synced to Salesforce.
It is recommended to first create a field mapping with only the string type fields of Salesforce initially. Once the sync starts working you can create mappings with other types of Salesforce fields as well.

[MO_CONTACT_US]