Differences between Classic Server Connector and the new Server Connector

Differences in setup


Classic Server ConnectorNew Server ConnectorNotes

Need Jira on SSL?

(error)

(tick)Jira on SSL is required to connect with Salesforce with the new Server Connector whereas on Classic it is optional.
Easy setup via Salesforce-managed package?

(error)

(tick)

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

The new Server Connector simply uses a Salesforce-managed package.

Apex triggers and Visualforce panels?(tick)(tick)
Jira can connect to multiple Salesforce instances?

(tick)

(tick)
Salesforce can connect to multiple Jira instances?(tick)(error)With the new Server Connector, Salesforce can only connect to 1 Jira.
Manual & auto bi-directional syncing?(tick)(tick)
Salesforce attachments are created as native attachments in Jira?

(tick)

(tick)

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

Jira attachments can be pushed and created as native attachments in Salesforce?(error)(tick)In Classic, Jira attachment cannot be pushed to Salesforce.
Compatible with Salesforce Files object type?(error)(tick)
Authentication using JWT and OAuth?

(error)

(tick)

In Classic, login is using only basic authentication.
Salesforce user does not require user to log in to Jira?(error)(tick)In the new Server Connector, authentication operations are done through the backend for a seamless user experience.
Diagnostics Table?(tick)(error)
Errors Logged in Jira Logs?(tick)(tick)
Support for Visualforce (Classic) UI?(tick)(tick)
Support for Lightning UI?(error)
Support for standard and custom Salesforce objects?(tick)(tick)

Differences in working with Jira


ClassicNew Server Connector
Object mapping concept
  • Connection holds authorization details for a single Salesforce instance
  • Mapping Scheme binds Jira issue type with Mapping. A Mapping Scheme can be assigned to a Jira project
  • Mapping defines the Field Mapping and field value mapping between Jira and Salesforce
  • Connection holds authorization details for a single Salesforce instance, and defines a selection of Salesforce objects made available through the Connection
  • Binding holds a 1-to-1 mapping of a Jira project and a Connection, as well as 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
Associate Salesforce records
  • Using Remote System ReferenceRemote 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 Remote Issue Link
  • Using Association to enable synchronization functions or simple linking
  • Association is shown in Salesforce section in a Jira issue panel. The fields displayed in this panel can be configured through Available Objects setting in Connection
  • The Connector does not provide any Jira custom fields
Create Salesforce records
  • Manual: Using Create New Object from this Issue in Remote System Reference
  • Auto: Using Push To Remote System post function
  • Manual: Using Create Salesforce Object button in Jira issue panel
  • Auto: Using Create Salesforce Object post function
Get updates from Salesforce

Manual: Using Pull Changes in Remote System Reference

Manual: Using Pull button in Jira issue panel
Send updates to Salesforce
  • Manual: Using Push Changes in Remote System Reference
  • Auto: Automatically enabled via Remote System Reference
  • Manual: Using Push button in Jira issue panel
  • Auto: Either using Push to Salesforce post function, or Auto-push setting in Association
Comments in Jira
  • 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 or off. A plain text label is appended to these comments to show its origin.
  • Comment filter: Salesforce comments can be filtered according to privacy setting (All, Public, Private). Tagging is not possible.
  • Salesforce comment is displayed as view-only under a dedicated 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), as well as specific hashtags.
JQL functions

Two functions available:

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

Not available. However, see "Reporting".

Search for Salesforce recordsNot availableA dedicated page to search for Salesforce objects, which also allows direct association and Jira issue creation from the search results
ReportingNot available. See "JQL functions"A dedicated reporting page to query associated with Jira issues, show the count of associations for each and export the results.
Bulk operations

Available:

  • Bulk push updates
  • Bulk pull updates
  • Bulk create

Available:

  • Bulk push updates

Differences in working with Salesforce


ClassicNew Server Connector
Associate Jira issues

Using Visualforce button utilizing API endpoint provided by the Connector. Requires the current Salesforce user to have an account in Jira.

  • Using Associate button in Jira Issues panel. Does not require the Salesforce user to have an account in Jira
  • All functions are available from within Salesforce interface
Create Jira issues
  • Manual: Using Visualforce button utilizing 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 the Connector
  • Manual: Using Create Jira Issue button in Jira Issues panel. Does not require the Salesforce user to have an account in Jira.
  • Auto: Using Apex trigger utilizing API endpoint provided by the Connector.
  • All functions are available from within Salesforce interface.
Get updates from Jira
  • Manual: Using Visualforce button utilizing 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 the Connector.
  • Manual: Using Pull button in Jira Issues Visualforce page. Does not require the Salesforce user to have an account in Jira
  • Auto: Not available
  • All functions are available from within Salesforce interface
Send updates to Jira
  • Manual: Using Visualforce button utilizing 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 the Connector
  • Manual: Using Push button in 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 the Connector
  • All functions are available from within Salesforce interface
REST API Endpoints for ApexAvailable
  • Not available
  • End user features (buttons, links) are pre-built in Lightning or Visualforce components
Comments in SalesforceJira comment is created as native comment in Salesforce. Plain text label is appended to these comments to show origins.
  • Using Jira Comments panel. Each comment shows the originating Jira issue key
  • Comment filter: Jira comments can be filtered according to specific tags
Chatter SupportNot available
  • Jira comments can be posted as a Chatter post for Cases objects
  • Chatter post can appear in Jira under a dedicated Salesforce Comments tab
Custom buttonsPossible through Apex and Visualforce componentsNot available
Jira ProjectsOnly Jira Projects with mapping appear to user when creating a Jira issue from Salesforce.Only Jira Projects with binding appear to user when creating a Jira issue from Salesforce. Also, admins can select available projects manually to further restrict the list.