• Jira Server

• Jira Cloud
• Jira Server
• Full Salesforce Lightning compatibility

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

• A Connection holds authorization details for a single Salesforce instance
• A Mapping Scheme binds 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 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.

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 in Salesforce
• This can be switched on/off, applies to all-or-none
• This connector also supports Lightning, thus, is 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 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.

• 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 Association.
• Auto: Using Create Salesforce Object post function.

Manual: Using Pull Changes in Remote System Reference.

• 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/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:

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

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".

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.

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

• Manual: Using Create Jira Issue 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 connector. See Configuring Automatic Jira Issue Creation from Salesforce

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

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

• Manual: Using Visualforce button utilizing API endpoint provided by connector. Requires the current Salesforce user to have an account in Jira.
• Auto: Using Apex trigger utilizing API endpoint provided by 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 connector. See Configuring Automatic Pull from Salesforce.

• 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.