This article describes a Trigger concept in Exalate.
You can start issue synchronization automatically according to a specified search query with the help of a trigger.
If the issue fits a search query it is triggered for synchronization automatically. Once someone updates the issue which is under sync the changes are synchronized automatically.
Every issue tracker has its own search query language. Since Exalate supports different issue trackers the search syntax may vary.
Jira JQL query
When you create an issue in project BLUE with label sync, that issue will start synchronization automatically.
Also, the same trigger will start the synchronization if any issue in project BLUE has been updated with label sync.
GitHub search query
Exalate app for GitHub uses GitHub advanced search syntax to filter issues in the trigger.
ServiceNow search query
Exalate app for ServiceNow uses ServiceNow search syntax to filter incidents in the trigger.
Azure DevOps search query
Triggers use a WIQL (Work Item Query Language) to search Azure DevOps work items. Use the Work Item Query Language Syntax to create a search query.
You only need the conditions found in the WHERE clause of the WIQL to filter the work items. Check the example below:
For more examples check this page.
HP ALM/QC search query
Zendesk search query
Exalate app for Zendesk uses Zendesk search syntax for the filter query. Below you can see an example:
Salesforce search query
Exalate app for Salesforce uses Salesforce Object Query Language to filter objects in a trigger.
You only need the conditions found in the WHERE clause of the SOQL for the trigger. The entity type should be selected from the list before specifying the search query. Check the example below:
How to create a trigger?
What if the connection used for a trigger has been disabled?
Whenever a connection used in a particular trigger is disabled, Exalate will still collect all the changes which are related to issues that are under sync using that connection.
The changes will be queued as sync requests. Once the connection is reenabled, sync transactions can continue from the point where they have been paused.
What if the trigger has been disabled?
Disabling the trigger makes Exalate ignore the create/update events for the issue that is matching the query.
- Start sync in Exalate for GitHub
- Confluence: trigger page sync
- Zendesk: trigger ticket sync
- Start sync in Exalate for ServiceNow
- HP ALM/QC: trigger defects/test cases synchronization
- Jira: triggering a synchronization
- Start sync in Exalate for Salesforce
Back to General Exalate concepts