Classic Connector and NextGen Connector for Salesforce & Jira comparison
The following table charts the differences between the Classic and NextGen editions of Salesforce & Jira Connectors.
On this page: |
---|
 | Classic Connector for Salesforce & Jira | Connector for Salesforce & Jira |
---|---|---|
Platform |
|
|
License | 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. |
Authentication Type | Secured basic authentication | OAuth2 |
Object mapping concept |
|
|
Sync direction | Manual & auto bi-directional is available | Manual & auto bi-directional is available |
Attachments |
|
|
Support for custom Salesforce Objects |
|
|
Jira feature differences | ||
Associate Salesforce Objects |
|
Except for JQL associations and association count |
Object mapping concept |
|
|
Create Salesforce Objects |
|
|
Get updates from Salesforce | Manual: Using Pull Changes in Remote System Reference. |
|
Send updates to Salesforce |
|
|
Comments in Jira |
|
|
JQL functions | Two functions available:
| Two functions are available:
|
Reporting | 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 |
Search page |
| A dedicated page to search for Salesforce objects, which also allows direct association and Jira issue creation from the search results. |
Bulk operations | Available:
| Available:
|
Salesforce feature differences | ||
Associate Jira issues | Uses the Visualforce button utilizing an API endpoint provided by connector. It requires the current Salesforce user to have an account in Jira. |
|
Create Jira issues |
|
|
Get updates from Jira |
|
|
Send updates to Jira |
|
|
Comments in Salesforce |
|
|
Chatter Support |
|
|
Implementation in Salesforce | 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. |
REST API Endpoints for Apex | Available |
|
Custom buttons | Possible through Apex and Visualforce components | Not available |
Jira Projects | Only Jira Projects with mapping appear to the user when creating a Jira issue from Salesforce. |
|
Differences in setup
 | Classic Server Connector | New Server Connector | Notes |
---|---|---|---|
Need Jira on SSL? | Jira on SSL is required to connect with Salesforce with the new Server Connector. It is optional on Classic. | ||
Easy setup via Salesforce-managed package? | Classic requires manual setup by Salesforce admins using Apex classes, triggers, and Salesforce. The new Server Connector uses a Salesforce-managed package. | ||
Apex triggers and Visualforce panels | Â | ||
Jira can connect to multiple Salesforce instances. | Â | ||
Salesforce can connect to multiple Jira instances. |
| To set up for new Server Connector, read this documentation: Setting up multiple Jira site integration | |
Manual & auto bi-directional syncing? | Â | ||
Salesforce attachments are created as native attachments in Jira? | In Classic, all Salesforce attachments are either displayed as view-only in the Remote Attachments tab OR pushed to Jira as a native attachment. | ||
Jira attachments can be pushed and created as native attachments in Salesforce? | In Classic, Jira attachment cannot be pushed to Salesforce. | ||
Compatible with Salesforce Files object type? | Â | ||
Authentication using JWT and OAuth? | In Classic, login uses basic authentication. | ||
Salesforce user does not require user to log in to Jira? | 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. | ||
Diagnostics Table? | Â | ||
Errors Logged in Jira Logs? | Â | ||
Support for Visualforce (Classic) UI? | Â | ||
Support for Lightning UI? | Â | ||
Support for standard and custom Salesforce objects? | Â |
Â