/
Configure Chatter

Configure Chatter

This guide explains enabling Chatter integration in Salesforce. With this feature, Jira comments can either be posted to Case Feed (Chatter) or Chatter comments can be posted to an associated Jira issue. This is currently only supported for Case objects.

When someone creates or edits a comment in Jira, a post will be made to the Case Feed of the corresponding associated Case object and vice versa. 

The post is made if:

  • Chatter Feed setting is enabled in Salesforce, per the guide below.

  • The Jira or Chatter comment satisfies comment privacy and hashtag filters set by the admin.

  • The associated Jira issue is not marked as View-only.

The Chatter post is posted by the administrator account configured for the connection. This behavior cannot be changed due to limitations in the Salesforce Chatter API. A remark, however, is provided to indicate the actual user who left the comment in Jira.

To enable Chatter integration in Jira, visit Configuring connection settings in Jira.

Enable Chatter Feed

  1. Log into your Salesforce and click Settings > Setup.
    If you are using Salesforce Classic, click Setup located on the upper right pane.

  2. In the sidebar, use Quick Find and type Installed Packages, then click the Installed Packages link that appears.

  3. Look for Jira for Salesforce and click Configure.

  4. On the Comment Configuration section, enable the toggle next to Chatter Feed.

Next steps

Related information

Related content

View Salesforce comments in Jira
View Salesforce comments in Jira
More like this
Configure Jira Comments (NextGen) with Lightning Experience
Configure Jira Comments (NextGen) with Lightning Experience
More like this
View Jira comments in Salesforce
View Jira comments in Salesforce
More like this
Configure settings in the Salesforce Package
Configure settings in the Salesforce Package
Read with this
Filter Jira comments in Salesforce Cases
Filter Jira comments in Salesforce Cases
Read with this
Set up a connection to Jira
Set up a connection to Jira
Read with this