Key Takeaways
- zAgileConnect enables integration of multiple Salesforce instances with one Jira instance, easing company acquisitions and transitions.
- Existing customers enjoy bi-directional Salesforce-Jira integration with automatic updates.
- Enhanced features include directed comments, bulk processes, and consolidated Salesforce properties in Jira.
Up to now, zAgileConnect supported integration of a single Salesforce instance with a single Jira instance. That addresses the typical scenario for most customers.
However, companies sometimes wish to integrate multiple production Salesforce instances with a single Jira instance. The most common reason is when one or more other companies are acquired, and it’s too complex and/or time-consuming to consolidate multiple Salesforce instances into one, or some transition time is needed to fully merge the separate Salesforce orgs.
zAgileConnect 1.14 now includes this capability for Jira Cloud, i.e. to integrate multiple Salesforce instances with one Jira Cloud instance. Users in each Salesforce instance see Jira as they do now, connecting an individual Salesforce instance to a single Jira instance.
For existing zAgileConnect customers, all functionality of bi-directional integration between Salesforce and Jira functions as it does for the current 1:1 integration. Updates from Jira are automatically applied to the appropriate Salesforce instance with which an Issue is associated.
The enhancement covers everything typically expected of zAgileConnect integration, taking into account the multiple Salesforce instances scenario:
- Comments: Comments posted to Salesforce objects from Jira are directed to the Salesforce instance.
- Attachments: Attachments posted to Salesforce objects from Jira are directed to the appropriate Salesforce instance.
- Bulk/Batch processes: support both Salesforce instances.
- Salesforce Properties within Jira: The Salesforce Properties panel in Jira displays a consolidated view of properties configured in different Salesforce instances for any object integrated with Jira.
Each Salesforce instance maintains its own zAgileConnect package configuration. These configurations are not shared across Salesforce instances linked to a single Jira. Importantly, the relationship between Jira issues and Salesforce objects will not be shared or visible to other Salesforce instance.
zAgileConnect 1.14 also includes:
- Custom Permissions for the following:
- Restrict access to Jira Issues transitions from Salesforce.
- Allow login to Jira from Salesforce using an individual user account.
- Allow login to Jira from Salesforce using Integration user account.
- Hide “Edit Issues” button in Related Jira Issues Lightning Web Component.
- Support for “Issue Linking” during Issue Create and Edit actions using respective Lightning Web Components.
- Post Comment to Jira Issue from Related Jira Issues Lightning Web Component.
- Upgraded API version of package components to v50 and greater.
For integration between a single Salesforce with multiple Jira instances or multiple Salesforce with a single Jira Data Center instance, or to learn more, contact sales@zAgile.com.
