This page describes how to synchronize worklogs information between two Jira instances.
Jira worklogs synchronization requires worklog author lookup. By default, Exalate tries to find the worklog author on the remote side and create a worklog on behalf of that author.
The author lookup is performed by email, but you can also configure other ways to find corresponding users on the local system (by full name, username or any other arbitrary logic that you might have).
Additionally, you can configure user mapping in the Incoming sync processors or set a default worklog author in case the original author is not found.
mergeWorkLogs helper method helps to merge worklogs:
- adds the added remote worklogs
- removes the removed
changes the changed ones
mergeWorkLogs does not touch any of the worklogs that exist only locally (were not synchronized yet or are filtered out from the synchronization)
To send worklogs to the Destination side use the code below
To add/update received worklogs from the source side use the code below.
Merges the worklogs from two sides and allows adjusting details of every synced workLog.
Worklog author user mapping
Exalate allows to map worklog authors, but in case the user from mapping settings is not found you can do the following:
- set the original worklog author if the originally mapped user is not found on the local side
- set a default worklog author if the originally mapped user is not found on the local side
Syncing Worklogs between Jira Cloud and Jira on-premise
This affects worklog synchronization since Exalate uses API to search by email. Therefore, worklogs will be synced only in case the user has set the email to be visible.
If you sync from Jira on-premise to Jira Cloud
If you sync from Jira Cloud to Jira on-premise
if you sync from Jira Cloud to Jira Cloud