Creating Jira Issues From Salesforce Objects

Lately we've been focusing more on the tracking and project management platform Jira. Atlassian's product isn't just a popular tool, it's quite flexible when paired with other systems, which makes it a great choice when working with large databases, supervising projects, or reporting and analyzing technical issues.

Many of our customers are using Jira in conjunction with other systems, but one of the more popular use cases is when Jira is integrated with Salesforce.

The two systems work great together not just for bug reporting, but for user enrichment as well. In today's post we'll show you how Salesforce and Jira operate together to create and update issues and objects in real time.

Integrate Jira and Salesforce with Cloudpipes

Synchronizing any channel with Cloudpipes is easy. Type the name of the channel you want Cloudpipes to connect with in the drop-down menu in the upper-right corner, and follow the steps. In the case of Jira you'll be asked to write your Jira server URL, login and password. Once you do that, click Connect.

For Salesforce all you need to do is to specify the type of account, and Cloudpipes will do the rest.

The pipeline we're about to construct will trigger every time when a new Salesforce object is updated. If we want a bi-directional synchronization between the Salesforce and Jira, we need to have another pipeline that will create Issues and Objects, which we can later link to other pipelines.


Next, we set up an IF/THEN condition that will specify under what conditions the pipeline will create issues in Jira. In this case we want issues to be created only after Cloudpipes verifies that there aren't similar issues already created, and by filtering Salesforce objects by record type.

If the above criteria are matched, Cloudpipes will then insert a Jira Issue with pre-mapped custom fields. That issue will be linked to the initial Salesforce object.

If the Salesforce record type is not matched, then the pipeline will go on to create a new Jira issue (but with a different issue type), and update the Salesforce object with the ID, key and status of the Jira issue that was created immediately before that.

Simultaneously, if the updated Salesforce object bears a different record type (Bug Report), then our pipeline will execute a different set of actions. It'll perform a Jira issue look up based on the initial Jira ticket ID. Then if found, will proceed to update that issue by priority and description.


If there's a mismatch with the Salesforce object's record type, then the pipeline will go on to do a look up for the Jira issue based on the predetermined criteria. If an issue is found that way, Cloudpipes will update its description

To run the pipeline all you have to do is click on the ON button and wait until the Cloudpipes syncs with both Jira and Salesforce.

This is just one example of how to do project management with Jira and Salesforce.

Found a better way to integrate Jira and Salesforce? Tell us more!