Accessing the configuration settings
Click Settings > Apps, and then in the sidebar, under CONNECTOR FOR SALESFORCE, choose Connections.
Select a connection, then click Configure.
Available Salesforce Objects
Objects and fields selected here are visible to end users through various connector features in Jira.
For more information, see Configuring Field Displays and accessing the Details Display screen.
Jira Notification Settings
These settings allow the configuration of notifications when a comment for Jira users is made in a Salesforce Case.
Enable or disable notifications for the following users:
All recipients of Issue Commented event
Current Assignee
Reporter
All Watchers
All Voters
Groups
For more information, see Configuring email notifications to notify Jira users.
Connection Settings
Enable or disable the Connection Settings options:
Allow Modification
If disabled, the connection will be in read-only mode. This setting has the highest precedence and overrides other settings.
Disable this setting if you need to immediately stop any synchronization.
Allow Automatic Push
If disabled, the auto push is not allowed to function in all current and new associations.
If enabled, the auto push is allowed to function in all current and new associations.
Allow Automatic Pull
If disabled, the auto pull is not allowed to function in all current and new associations.
If enabled, the auto pull is allowed to function in all current and new associations. Apex trigger must be configured for the associated object type.
Salesforce Auto Assign
If enabled, active assignment rules will be used when creating or updating Case and Lead objects.
Attachment Settings
For more information about file attachments, view Working with attachments.
Synchronize Attachments
If enabled, files attached to associated issues and Salesforce objects will be synchronized.
Create Salesforce Attachment as Files
If enabled, files will be uploaded as Salesforce files, not attachments. Requires Synchronize Attachments to be Enabled.
This setting is recommended if you use Salesforce Lightning.
Comments & Chatter Settings
Comment Privacy
Determines visible Salesforce Case comments based on their privacy.
Available Options: All Comments, Public Comments Only, Private Comments Only.
Comment Tag Filter
Separate each tag in the list by a space to filter Salesforce comments (e.g. '#Jira #Jira-service-management').
If configured, only Salesforce comments with at least one of the tags in their body will be displayed.
Show Chatter Feeds
If enabled, Chatter feeds will be shown in the Salesforce Comments tab.
For more information, see Working with comments.
With Lightning Experience, the way you can view Chatter feeds is different, read https://appfire.atlassian.net/wiki/spaces/CSFJIRA/pages/470803350/Configuring+Jira+Comments+NextGen+with+Lightning+Experience#Adding-Comments-in-Salesforce-(Chatter-Feed-and-Case) for more information.
Query Optimization
Optimize the association JQL query
If enabled, this option can help improve performance by fine-tuning the JQL query that retrieves Salesforce and Jira associations, where it will be limited to projects with active binding. This option is disabled by default because the issue usually only affects projects with a very large number of Jira issues (around 5,000 or more).
Default Presets
These settings allow admins to set defaults for what happens when a user creates or associates a Jira Issue/Salesforce Object.
Force All Presets
Enabling this will allow admins to force all the presets that have been set below, both inside Jira and Salesforce. This will also completely hide the presets from being shown to users when they create or associate a JIRA Issue/Salesforce Object.
View Only
If enabled, new associations will be set to View Only by default when users create or associate a Jira Issue/Salesforce Object.
Automatic Push
If enabled, new associations will be set to Automatic Push by default when users create or associate a Jira Issue/Salesforce Object.
Automatic Pull
If enabled, new associations will be set to Automatic Pull by default when users create or associate a Jira Issue/Salesforce Object.
After Associating
Admins can set the default action that happens immediately after an association.
Available Values:
Do nothing
Push to Salesforce
Pull from Salesforce
Push to Salesforce then Pull from Salesforce
Pull from Salesforce then Push to Salesforce
After Creating Jira Issue
Admins can set the default action that happens immediately after Jira Issue creation.
Available Values:
Do Nothing
Push to Salesforce
After Creating Salesforce Object
Admins can set the default action that happens immediately after Salesforce Object creation.
Available Values:
Do Nothing
Pull from Salesforce
