Search this space

Live demo

Want to see a live demo and learn what this Connector can do? Join our jam sessions!

Page tree

If you are looking for documentation for the new Salesforce & JIRA Cloud Connector, click here.

Skip to end of metadata
Go to start of metadata

Introduction


There are 3 different types of functionality for linking JIRA with Salesforce.com. It is possible to mix and match options to best fit your needs. Which combination you use depends on your needs. 

The 3 different options are:

Remote System Reference


This is typically referred to as the "synchronization" functionality, which is bi-directional. This allows you to create an association between a JIRA issue and any Salesforce.com object (e.g. Case, Account, Solution, Opportunity, custom objects, etc.).

Once associated, you can then "share" information across the two systems such that when the Salesforce.com object is updated, the JIRA issue is updated as well. Likewise, when the JIRA issue is updated, the Salesforce.com object is updated. You are able to control what fields are updated in each system with our flexible Mapping Configurations. In addition, comments are also automatically synchronized across the two systems.

This synchronization can be used in conjunction with the Remote Object Link option to create associations with multiple Salesforce.com object types.

For example, you can use the Remote System Reference to link the issue with a Salesforce.com Case and then configure additional Remote Object Link references for the Account, Contact and Owner. The associated values can be mapped using our Mapping Configurations, and by doing so, the system will automatically pull across the Account, Contact and Owner of the Case when the issue is created or synchronized.

For more details and an example on when to use this option, consult the Remote System Reference page.


This is part of the "non-synchronization" stack that is available for JIRA 4.3 and higher. This allows you to create "Custom Fields" which are used to associate a JIRA issue with any Salesforce.com object. This can either be a 1 to 1 (using the Remote Object Link custom field) or a 1 to many configuration (using the Multi Remote Object Link custom field).

Using this method, you are still able to see the various attributes of the Salesforce.com object (configurable to display various fields of the object), however you will not be able to update the fields of the linked Salesforce.com object from within JIRA (you will have to log into Salesforce.com to do this). In a way, it is only a read-only method from JIRA.

For more details and an example on when to use this option, consult the Remote Object Link page.


This is a simplified version of the Remote Object Link option and is only available for JIRA 5.0 and later. Like the Remote Object Link, it provides a read-only view of linked Salesforce.com objects and supports many to many associations. Unlike the Remote Object Link, it is very simple to configure (this method only requires the Connection to be configured) and it stores some of the information from the Salesforce.com object so that it is still accessible if Salesforce is unavailable. For example, Cases will continue to display the Subject field.

For more details and an example on when to use this option, consult the Remote Issue Link page.

Differences Between Options


The table below summarizes the differences between the options:

 

Remote System Reference

Remote Object Links

Remote Issue Links

Link to Salesforce.com

(tick)

(tick)

(tick)

Custom display configuration

(tick)

(tick)

(tick)

Configuration required

(tick)

(tick)

(error)

Workflow custom field features such as validation

(tick)

(tick)

(error)

Searchable in JIRA

(tick)

(tick)

(error)

Relationship visibility in Salesforce

(tick)

(tick)

(error)

Data availability when Salesforce down

(tick)

(error)

(tick)

Synchronize to/from Salesforce

(tick)

(error)

(error)

Comments synchronization

(tick)

(error)

(error)

More API calls

(tick)

(error)

(error)

Auto-lookup to Salesforce

(error)

(tick)

(error)

Associate to multiple links in Salesforce

(tick)

(tick)

(tick)

Associate to multiple Salesforce object types

(error)

(tick)

(tick)

Synchronize Remote Attachment

(tick)

(error)

(error)

Page Contents

Want help getting the Connector setup and configured in your environment? Let our team do the work.

  • No labels