The following table charts the differences between the two editions of Salesforce & Jira Connectors.
|Classic Connector for Salesforce & Jira||Connector for Salesforce & Jira|
|License||Available through both Atlassian Marketplace and ServiceRocket Marketplace.|
Available through Atlassian Marketplace only. Monthly subscriptions are the default option, however discounted annual subscriptions are available upon request to our Atlassian Sales team.
|Authentication Type||Secured basic authentication||OAuth2|
|Object mapping concept|
|Sync direction||Manual & auto bi-directional is available|
Manual & auto bi-directional is available
|Support for custom Salesforce Objects|
|Associate Salesforce Objects|
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 Remote Issue Link.
Using Association to enable synchronization functions or simple linking.
Association is shown in Salesforce section on the right side panel of a Jira issue. The field displayed in this panel can be configured through Available Objects setting in Connection.
The connector does not provide any Jira custom field.
|Create Salesforce Objects|
|Get updates from Salesforce|
Manual: Using Pull Changes in Remote System Reference.
|Manual: Using Pull button in Association.|
|Send updates to Salesforce|
|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/off. Plain text label is appended to these comments to show origins.
Comment filter: Salesforce comments can be filtered according to privacy setting (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), as well as specific tags.
Two functions available:
A primitive JQL field is available for now e.g. "salesforceAssociatedTypes is not NULL" to retrieve all Jira issues with associations.
Not available. However, see "Reporting".
|Reporting||See "JQL functions".||A dedicated reporting page to query associated Jira issues and show the count of associations for each.|
|Search page||A dedicated page to search for Salesforce objects, which also allows direct association and Jira issue creation from the search results.|
|Associate Jira issues|
Using Visualforce button utilizing API endpoint provided by connector. Requires the current Salesforce user to have an account in Jira.
Using Associate button in Jira Issues Visualforce page. Does not require the Salesforce user to have an account in Jira.
|Create Jira issues|
|Get updates from Jira|
|Send updates to Jira|
|Comments in Salesforce||Jira comment is created as native comment in Salesforce. Plain text label is appended to these comments to show origins.|
|Implementation in Salesforce||Using Apex code to manually create Visualforce elements.||Using managed package installed from AppExchange. The package contains Visualforce elements.|