zAgileConnect 1.17

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 zAgileConnect Flow Action - Transition Issue by Status Name and zAgileConnect Flow Action - Transition Issue by Transition Name

• New Flow Actions to send comments and attachments to Jira. See zAgileConnect Flow Action - Create Issue Comment and zAgileConnect Flow Action - Send Attachment to Jira.

• New Flow action to retrieve Jira Issue data in real time and find Jira Users. See 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 zAgileConnect Flow Screen Components.

Enhancements:

• Support for MTLS and OAuth 2.0 Authentication to Jira Data Center and Jira Cloud via Named Credentials. See Enabling Connectivity between Salesforce and Jira via OAuth 2.0 Authentication

• zAgileConnect LWCs Related Jira Issues, Search Jira Issues and 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.