Jira Connector Release Notes

Request Participants Portal users cannot be added to the standard watcher list. To resolve this, a new “Request Participants” component has been implemented. It is available on the issue layout and requires enabling via the App Builder.

Global User Mapping The user mapping functionality has been completely redesigned. It is now global and ensures full alignment between Salesforce and Jira users. Configuration is available in the setup menu.

Creating Service Request Via Flow Users can now create Jira Service Requests directly via Salesforce Flow.

Manual Automation on Request Type Added the ability to configure mapping for the manual creation of Jira Service Requests.

Bulk Linking Users can now link multiple Jira issues to Salesforce objects in bulk.

Display Username In Comment Header When enabled, comments created in Salesforce will display a header that includes the Salesforce user’s name.

Add Jira Username To Comment Header When enabled, comments created in Jira will display a header that includes the Jira user’s name.

Sync Only Public JSM Comments Added an option to synchronize only public Jira Service Management (JSM) comments. Internal or private comments from Jira will not be visible in Salesforce when this is enabled.

Make Jira Comments Internal Only When enabled, all Jira comments synced to Salesforce Chatter will be visible only to internal users, restricting access for Community/Portal users.

Access Configuration Administrators can now control which Jira projects, issue types, and fields are accessible to specific Salesforce Profiles or Permission Sets. This applies within the context of a particular object (e.g., Case) and specific Record Types, ensuring users only see relevant options based on their access levels and business requirements.