Confluence has been updated to version 6.15.9

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.

If you don't see the Exalate operation on the issue view check the general settings to make sure the operation is enabled.



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

Exalate Trigger allows syncing issues automatically according to a specified search query.

Whenever an issue is created or updated and fits a search query it gets automatically synchronized according to a configured Connection. 

Once the issue is already under sync, any issue change would get synced until another behavior is configured in the Sync Rules. 

Example

You have a trigger with a following search query project = BLUE AND labels = sync and connection blue-red.

Whenever an issue is created in project BLUE with label sync, that issue gets automatically synchronized according to connection blue-red.

You don't need to click any button to start the synchronization. The issue is synchronized straight after its creation.

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


If you sync issues according to trigger project = BLUE and then move an issue which is under sync from project BLUE to project RED the synchronization will not stop.

You can stop the synchronization for an issue using Unexalate operation.

Alternatively, if you don't want to receive changes from the issue which has been moved to project RED you can configure the receiving side's change processor to return in case the remote issue does not meet certain criteria.



Configuring a trigger

Navigate to Triggers page from the Exalate admin menu


Create Trigger


  • input the desired search filter in the If field
  • specify the connection under which you would like the issues to be synced
  • add a note to keep a reference to the trigger
  • toggle to activate 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