How to Search Issues Under Sync with JQL Functions

In Exalate for Jira on-premise, you can search for issues under sync with JQL functions.

Note: In Exalate 4.7.2 and lower, JQL functions have shown performance problems when many issues are under sync.

Retrieve all issues that are under sync
Retrieve all issues that are stuck in sync
Other Useful Functions

Retrieve All Issues that are Under Sync

To retrieve issues that are under sync, use the following function:

issue in under_sync()

Retrieve All Issues that are Stuck in Sync

To retrieve issues that are stuck in sync, use the following function:

issue in sync_stuck ()

This function gets different results based on the arguments that you enter.

Possible results:

Retrieve all issues that are stuck in sync for more than one hour:
```
issue in sync_stuck()
```
Retrieve all issues that are stuck for more than one hour for a specific connection:
```
issue in sync_stuck("Connection name")
```
Connection name -- the name of the connection.
Retrieve all issues that are stuck in sync for a number of hours:
```
issue in sync_stuck("3")
```
3 -- the number of hours
Retrieve all issues for a specific connection that are stuck in sync for a number of hours:
```
issue in sync_stuck("2", "Connection name")
```
2 -- the number of hours.
Connection name -- the name of the connection.

Other Useful Functions

Filter Synced Issues by the Connection Name

issue in under_sync_by_connection("Connection name")

Filter Synced Issues by Instance

Note: The function works for Exalate 3.x and lower versions.

issue in under_sync_with_instance("Instance name")

Filter Issues in a Project which are Not Yet Synchronized

project = ABC and issue not in under_sync()

Find Local Issue using Remote Issue Key

Create a single-line text custom field "External issue key" and sync the remote issue key into the custom field. Then filter the local issues using the custom field data, which includes the remote issue key.

Note: In order to sync the remote issue key into the custom field, you should add the following line to both the Create and Change processors on the Destination side:

issue.customFields."External issue key".value = replica.key

Then you must trigger sync on the Destination side so that the change processor would execute on the Source side. You can use Bulk Exalate or the standard bulk change feature to force update sync for multiple issues.

The JQL query to search the local issue by the remote issue key stored in the custom field is as follows:

"External issue key" = "EJIRAFICS-37"
//"External issue key" is  the custom field name and "EJIRAFICS-37" is the remote issue key