Supported in - JIRA SERVER JIRA CLOUD

The exalate operation for JIRA server

Once installed, every issue will have a new operation Exalate in the drop-down menu.

When triggering this action, a user will have the option to choose which connection to use to exalate it.

When the action is submitted, the synchronization engine will be triggered.

(warning) When the operation is missing from the menu, check the trigger operation configuration.

The exalate operation for JIRA cloud

Once installed, every issue will have a new operation Exalate in the drop-down menu and the Exalate button.

When triggering this action, a user will have the option to choose which relation to use to exalate it.

 

When the action is submitted, the synchronization engine will be triggered.

(warning) When the operation is missing from the menu, check the trigger operation configuration.

The exalate post function

Alternatively, an issue can be exalated by a post function.  

 

1Editing a workflow as detailed by Atlassian. Documentation
2Adding a post function. 
3Selecting and adding the 'exalate now' function. 
4Choosing the right connection. 

5

(warning) Important
Ensuring that the post function is executed after the issue has been updated
else the wrong status is transferred.

 


JQL Trigger

A JQL Trigger allows configuring Exalate such that whenever an issue is created or updated and fits a configured search query (for example: "project = BLUE AND labels = sync"), it gets automatically synchronized according to a configured Connection.

 

For example: if a Trigger is created with a search query "project = BLUE AND labels = sync" and connection "blue-red" then whenever an issue is created in project BLUE with label sync, that issue gets automatically synchronized according to connection "blue-red" (there's no need for a user to click any button, there's also no need to configure workflow post-functions, the issue is synchronized straight after it's creation). Also, given the same trigger, if an issue was created in project BLUE, and later was set with label "sync", the issue would get synchronized automatically straight after that update.

 

Configuring a trigger

Configuring a trigger is simple, first, you will need to access the trigger page:

Click "Create Trigger" button to add a new trigger

 

Input the desired JQL filter and specify under which connection you would like to exalate the issues matching that condition. If desired, a Note can be added to keep a reference to the 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.

Example

JQL with userNames

issuetype = Bug AND assignee in (mia) AND reporter in (alana) order by lastViewed DESC

JQL with account IDs

issuetype = Bug AND assignee in (abcde-12345) AND reporter in (abc551-c4e99) order by lastViewed DESC

Bulk Exalate

Bulk Exalate allows to trigger synchronisation on a batch of issues. 

In order to perform Bulk Exalate, you need to create a trigger with a search query that select all those issues (for example "project = BLUE AND components = External"), and then use "Bulk Exalate" action on that trigger

To run a trigger immediately, click Bulk Exalate in the Action section. The synchronization will start for all issues related to this trigger except for the issues that were already synchronized.

 

 

See Also

Triggering synchronization for HP QC/ALM