In Exalate, there are multiple ways to start syncing issues in Jira:
After you install Exalate, every issue will have a new issue action Exalate.
To start the issue synchronization click the Exalate button, then select a connection that should be used to use to synchronize issues.
The Exalate issue operation is located under More tab on the issue view
You can find the Exalate button on the right sidebar on the issue view.
Exalate Now post function
You can start the synchronization automatically with the help of Exalate Now post function in Jira.
Follow the steps below to configure the Exalate Now post-function:
1. Navigate to edit the workflow in Jira admin
You can edit a Jira workflow under→ Issues → Workflows
Check out advanced workflow configuration in Jira for more details.
2. Click on the transition and select Post Functions
3. Add a post-function to your workflow
3. Select Exalate Now post function
4. Select a connection
5. Ensure that the Exalate Now post function is in the correct order
You need to make sure that the post function is executed once the issue has been updated otherwise, the issue will be transferred to the wrong status.
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.
Check the example of the JQL trigger query below.
When you create an issue in project = BLUE with labels = sync issue will be synchronized automatically.
Also, the same trigger will start the synchronization if any issue in project BLUE has been updated with label sync.
Using saved filters
You can use JQL saved filters in trigger configuration. Please makes sure that the filter is shared with the proxy user.
Filters can be shared with other users via user groups, projects, and project roles. They can also be shared globally. Any filter that is shared is visible to users who have the Administer Jira global permission.
Use filter ID (filter = 10500) or name (filter = "My filter") to configure a trigger
Changes due to compliance with GDPR
JQL query containing user identifiers such as username, display name or email will stop working starting from 29th of March due to Atlassian compliance with GDPR.
Update your JQL query to use account IDs instead. Find more details in REST API migration guide and deprecation notice - userName and userKey. You can get the user account IDs with the help of JIRA Cloud REST API.
JQL with userNames
JQL with account IDs
Before doing any bulk operation it is recommended to validate the configuration. You can test it by syncing one issue before you do Bulk Exalate to make sure the configuration works as expected.
Follow the steps below to Bulk Exalate issues.
1. Create a trigger
2. Click Bulk Exalate
Exalate will start the synchronization of all issues that fit the search query specified in this trigger.