zAgileConnect 1.17

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.