Salesforce and Jira Server Connector vs. Cloud Connector Comparison

• Jira Datacenter

• Jira Cloud

• Jira Datacenter

• Full Salesforce Lightning compatibility

Available through Atlassian Marketplace.

Available through Atlassian Marketplace only. Monthly subscriptions are the default option; however, discounted annual subscriptions are available upon request from our Atlassian Sales team.

Secured basic authentication

OAuth2

• A Connection holds authorization details for a single Salesforce instance

• A Mapping Scheme binds the Jira issue type with Mapping. A Mapping Scheme can be assigned to a Jira project

• A Mapping defines the Field Mapping and field value mapping between Jira and Salesforce

• A Connection holds authorization details for a single Salesforce instance and defines a selection of available Salesforce objects through the Connection.

• A Binding holds a 1-to-1 mapping of a Jira project, a Connection, and a Mapping configuration.

• Each Mapping configuration contains a Mapping of a Salesforce object and a Jira issue type, as well as Fields Mapping and Fields Value Mapping.

Manual & auto bi-directional is available

Manual & auto bi-directional is available

• All Salesforce attachments are either displayed as view-only in the Remote Attachments tab OR pushed to Jira as native attachment

• Jira attachment cannot be pushed to Salesforce

• Salesforce attachments are created as native attachments in Jira

• Jira attachments are created as native attachments or files in Salesforce

• This can be switched on or off and applies to all-or-none

• This connector also supports Lightning, so it's compatible with Files objects (primary attachment module in Lightning)

• Using Remote System Reference, Remote Object Link and Remote Issue Link.

• Remote System Reference enables synchronization functions, while Remote Object Link enables view-only information. These features are represented as custom fields in Jira, and the display output can be customized through the field configuration.

• For simple linking purposes, use the Remote Issue Link.

• Using Association to enable synchronization functions or simple linking.

• Association is shown in the Salesforce section on the right-side panel of a Jira issue. The field displayed in this panel can be configured through the Available Objects setting in Connection.

• The connector does not provide any Jira custom field.

Except for JQL associations and association count

• A Connection holds authorization details for a single Salesforce instance

• A Mapping Scheme binds the Jira issue type with Mapping. A Mapping Scheme can be assigned to a Jira project

• A Mapping defines the Field Mapping and field value mapping between Jira and Salesforce

• A Connection holds authorization details for a single Salesforce instance and defines a selection of Salesforce objects made available through the Connection

• A Binding holds a 1-to-1 mapping of a Jira project, a Connection, and a Mapping configuration. Each Mapping configuration contains a Mapping of a Salesforce object and a Jira issue type, as well as Fields Mapping and Fields Value Mapping

• Manual: Using Create New Object from this Issue in Remote System Reference.

• Auto: Using Push To Remote System post function.

• Manual: Using the Create Salesforce Object button in Association.

• Auto: Using Create Salesforce Object post function.

Manual: Using Pull Changes in Remote System Reference.

• Manual: Using the Pull button in the Association tab in Jira.

• Using the Push button in the lightning component.

• Auto: Using Apex trigger utilizing API endpoint provided by connector. See Configuring Automatic Pull from Salesforce.

• Manual: Using Push Changes in Remote System Reference.

• Auto: Automatically enabled via Remote System Reference.

• Manual: Using Push button in Association.

• Auto: Either using Push to Salesforce post function, or Auto-push setting in Association.

• Salesforce comments are created as native comments in Jira. Selected Jira comments can be pushed to Salesforce as native comments.

• This can be switched on and off. Plain text label is appended to these comments to show origins.

• Comment filter: Salesforce comments can be filtered according to privacy settings (All, Public, Private).

• Salesforce comments are displayed as view-only under the Salesforce Comments tab in Jira. Each comment contains a link to the originating Salesforce object.

• Comment filter: Salesforce comments can be filtered according to the privacy setting (All, Public, Private) and specific tags.

Two functions available:

• remoteObjects(field, value)

• remoteObjects(field1, comparator1, value1, field2, comparator2, value2, ...)

Two functions are available:

• JQL associations

• JQL association count

See JQL functions

A dedicated reporting page to query associated Jira issues and show the count of associations for each.

As well as JQL functions and fields

A dedicated page to search for Salesforce objects, which also allows direct association and Jira issue creation from the search results.

Available:

• Bulk push updates

• Bulk pull updates

• Bulk create

Available:

• Bulk push updates

• Bulk Associate Salesforce records

• Bulk push can be done using the Post Function

• Bulk create is possible using the Post Function (the limit is one Salesforce record per Jira issue

Uses the Visualforce button utilizing an API endpoint provided by connector. It requires the current Salesforce user to have an account in Jira.

• Uses the Associate button on the Jira Issues Visualforce page. Does not require the Salesforce user to have an account in Jira.

• Manual: Uses a Visualforce button utilizing an API endpoint provided by a connector. The current Salesforce user must have an account in Jira.

• Auto: Using Apex trigger utilizing API endpoint provided by the connector.

• Manual: Uses the Create Jira Issue button in the Jira Issues Visualforce page/ Aura and Lightning Web Component. It does not require the Salesforce user to have an account in Jira.

• Auto:  Using Apex trigger utilizing API endpoint provided by connector. See Configuring automatic Jira issue creation from Salesforce.

• Manual: Uses the Visualforce button utilizing the API endpoint provided by the connector. Requires the current Salesforce user to have an account in Jira.

• Auto: Using Apex trigger utilizing API endpoint provided by connector.

• Manual: Uses the Pull button in Jira Issues Visualforce page. Does not require the Salesforce user to have an account in Jira.

• Auto: Push to Salesforce post function or Auto-push setting in Association.

• Manual: Uses a Visualforce button utilizing an API endpoint provided by a connector. Requires the current Salesforce user to have an account in Jira.

• Auto: Using Apex trigger utilizing API endpoint provided by connector.

• Manual: Uses the Push button on the Jira Issues Visualforce page. Does not require the Salesforce user to have an account in Jira.

• Auto:   Using Apex trigger utilizing API endpoint provided by connector. See Configuring Automatic Pull from Salesforce.

• Jira comments are created as native comments in Salesforce.

• A plain text label is appended to these comments to show origins.

• Using Jira Comments Visualforce page. Each comment shows the originating Jira issue key.

• Comment filter: Jira comments can be filtered according to specific tags.

• Jira comments can be posted as a Chatter post.

• Chatter post to Jira comment is coming soon.

Using Apex code to manually create Visualforce elements.

Uses a managed package installed from AppExchange. The package contains a lightning component (two for Jira issues and two for comments). One is the NextGen and the old one for compatibility issues) and a Visualforce component.

Available

• Not available

• End user features (buttons, links) are pre-built in Lightning or Visualforce components

Possible through Apex and Visualforce components

Not available

Only Jira Projects with mapping appear to the user when creating a Jira issue from Salesforce.

• Only Jira Projects with binding appear to the user when creating a Jira issue from Salesforce.

• Admins can select available projects manually to further restrict the list.

• There is a setting to allowlist/blocklist projects

Jira on SSL is required to connect with Salesforce with the new Server Connector. It is optional on Classic.

Classic requires manual setup by Salesforce admins using Apex classes, triggers, and Salesforce.

The new Server Connector uses a Salesforce-managed package.

To set up for new Server Connector, read this documentation: https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/470752838

In Classic, all Salesforce attachments are either displayed as view-only in the Remote Attachments tab OR pushed to Jira as a native attachment.

In Classic, Jira attachment cannot be pushed to Salesforce.

In Classic, login uses basic authentication.

In the new Connector, authentication operations are performed through the backend for a seamless user experience.

DC has an integration user(needs to be set up as part of the configuration)

Cloud has an integration user created when the plugin is installed.