Release 1.17.2
Release Date: April 21, 2026
Enhancements:
-
Support for new Salesforce SLDS v2 style in Lightning pages and components.
-
Improved UI for configuring Jira Projects and Issue Types.
-
Improved error notifications via email in the Salesforce package for background operations.
-
Support for special text fields (email, URL, etc) linked to Jira Issue text fields in JSM forms.
-
Column resizing on Related Jira Issues LWC is now persisted in the browser local storage.
-
Support for labels with white spaces in flow actions for create/edit Issues (will replace white spaces with underscores).
-
Improvements for paragraph JSM fields.
-
Security improvements.
Fixes:
-
Fix for error handling when re-authenticating to Jira and Salesforce IPs are blocked.
-
Creating new JSM requests UI fail to load if any configured service desk space is deleted or access is removed.
-
“View All” mode in Related Jira Issues was not honoring unlink/delete custom permissions.
-
Unable to re-authenticate to Jira in Salesforce sandboxes after sandbox refresh when using OAuth 2.0.
-
Null values for customs fields cause errors in create / update Issue flow actions.
-
Login option missing in “Related Jira Issues“ component when “View Setup” permission is not granted.
Jira Data Center add-on only update (1.17.1-11, 1.17.1-10 and 1.17.1-8)
Release Date: April 9, 2026
Enhancements:
-
Support for Jira 11.x.
-
Removed attachment size restrictions when using download locally for files stored in Salesforce (Attachments tab on Salesforce Object details popup).
-
Security improvements.
-
Support for linking to multiple Cases with #linktomulticase #casenumber1 #casenumber2.
-
Improved Attachment download locally streaming to prevent SocketTimeoutException.
Fixes:
-
Entity Properties configuration page not refreshing after save.
-
Salesforce properties not displayed properly on Agile view for large values.
-
Some zAgileConnect functionalities are not working properly when Jira is configured with context path.
-
Refresh Salesforce Properties option on Issue view conflicts with some Jira third-party Add-ons.
-
Send comment button hidden on send comment popup in some versions of Jira.
Release 1.17.1
Release Date: December 11, 2025
Enhancements:
-
Added affected Case Ids on email sent for synchronization errors with Jira.
-
Allow to re-authenticate in OAuth 2.0 from “Sign in to Jira“ page (it was also possible to do it from the external credentials Salesforce settings).
-
New validations to help troubleshoot authentication problems in OAuth 2.0 when using user named credential.
-
Activity LWC shows expanded content by default (same as activity widget in Jira).
-
Activity LWC links on titles now go to Salesforce Issue Details.
-
Allow selection of both packaged fields and custom fields for ZIssue mapping in Step 4 for Jira standard fields.
-
Prevent duplicate Issue creation in some scenarios where javascript remote actions are executed more than once.
-
Lightning console navigation for create Issue and update Issue (in console it will open a new tab instead of modal popup).
-
Support for paragraph JSM questions.
-
Refresh Salesforce properties in Jira allows refreshing only data with sync errors.
Bug Fixes:
-
CSV import does not work with big files.
-
Jira integration user not displayed for Jira connection when using OAuth 2.0 authentication to Jira.
-
Minor fixes on Flow screen components and JSM Forms.
-
CSV import progress bar screen stuck after job is aborted.
-
OAuth2.0 authentication fails when Jira username has spaces in Jira Data Center.
-
Time tracking Jira fields not being synchronized with Salesforce.
-
Jira Issue transitions getting loaded twice after updating one in Issue details visualforce page.
-
zAgileConnect Salesforce package does not allow authentication to Jira after a Salesforce sandbox refresh (OAuth 1.0).
-
Transition Issue screens not showing current Jira field values.
-
New Issue button does not work when only JSM projects are selected but no Jira projects.
-
Related Issues not refreshing after issue linking on console navigation when multiple related Issues LWCs are present (Multi-Jira connection).
-
Wrong error message “No access“ after authenticating to Jira directly from the Related Jira Issues LWC.
Release 1.17
Release Date: June 18, 2025
Features:
-
Support for JSM Forms attached to Request Types when creating from Salesforce. More details in Jira Service Management (JSM) Forms for Jira Cloud.
-
New Flow Actions to Create, Update, Link, Unlink and Delete Jira Issues.
-
New Flow Actions to Transition Issues by Status Name or Transition Name. More details in (V1.17) zAgileConnect Flow Action - Transition Issue by Status Name and (V1.17) zAgileConnect Flow Action - Transition Issue by Transition Name
-
New Flow Actions to send comments and attachments to Jira. See (V1.17) zAgileConnect Flow Action - Create Issue Comment and (V1.17) zAgileConnect Flow Action - Send Attachment to Jira.
-
New Flow action to retrieve Jira Issue data in real time and find Jira Users. See (V1.17) zAgileConnect Flow Action - Get Issue.
-
Create custom Create / Update Issue screens in Salesforce from provided Flow Screen Components for Jira standard and custom fields. More details in (V1.17) zAgileConnect Flow Screen Components.
Enhancements:
-
Support for MTLS and OAuth 2.0 Authentication to Jira Data Center and Jira Cloud via Named Credentials. See (V1.17) Enabling Connectivity between Salesforce and Jira via OAuth 2.0 Authentication
-
zAgileConnect LWCs (V1.17) Related Jira Issues, (V1.17) Search Jira Issues and (V1.17) Related Jira Activity can be included in Flow Screens.
-
zAgileConnect Salesforce package components upgraded to Salesforce v61.0 API version.
-
Support for “Parent“ Jira Issue field.
-
Ability to restrict sending Comments and Attachments from Salesforce via Custom Permissions in “Permission Settings”.
-
Ability to refresh the “Related Jira Issues” LWC from custom LWC components via “Related_Issues_Changed“ Lightning Message Channel.
-
Removal of ZIssue records with a batch job when a Jira Project is deleted.
-
Support for Atlassian API change in Jira Data Center 10.5 or newer when authenticating to Jira from Salesforce.
Bug Fixes:
-
Standard Jira Issue numeric fields configured to be pulled from Jira are stored as null values in Salesforce (for example Votes, Watchers, etc).
-
Improve handling for large size Issue data on Issue Details visualforce page.