Skip to main content
Skip table of contents

Making bulk changes to Salesforce and Jira mapping configuration by editing JSON files


As seen in the image below, mapping each Reporter field(Jira) to Owner ID(Salesforce) can take a long time. You will have to manually configure each field one by one.

By exporting the existing mapping, you will be able to extract the issue type ID and the Salesforce objects data into a .json file. 

This guide will help you use the exported JSON file to map user related fields such as assignee and reporter with new values and reimport it back into the Salesforce configuration page. 


1. Go to AppsSalesforce BindingsMapping > click on Export on the top right button.

2. You can use any open source editor, for the example, the Notepad++ text editor is used.

3. Open the Notepad++ application > on the navigation bar, select PluginsPlugins Admin

4. In the search box, type "json" and click Next.

5. Select "JSON Viewer" and click Install to install the latest JSON viewer available. You may be required to restart the application.

6. Open the unformatted .json file with the Notepad++ application. In the navigation bar, select Plugins > JSON Viewer >  Format JSON

7. In the formatted .json file, search for the Jira Issue Type ID of the existing mapping. 

How to get the Jira issue type ID:

Go to your Project > Project settings > Issues > Types > hover on the issue type link.

In the URL shown, the last numbers (ex, 10001) is the Jira issue type ID.

8. Once located, scroll until you find the assignee user ID with the Salesforce Owner ID value.  

9. Copy those lines to another issue type ID. With this, you can copy the user ID data within the file to other issue type IDs without the need to map them manually in the user interface.

Make sure the lines that are copied over have opening and closing brackets, else the file import will fail.

10. Once the file editing is complete, go to AppsSalesforce BindingsMapping > click on Import on the top right button and enter the file.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.