This page describes how to exchange worklogs information between two instances.
Worklog synchronization allows syncing work logs from one JIRA instance to another JIRA instance.
Exalate will try to find work log author and change author (by email).
If you configure work log synchronization by default, a user with email "email@example.com" logs work in a synchronized issue BLUE-1 (synced to issue RED-1).
The Exalate would attempt to find the user with email "firstname.lastname@example.org" on the Destination side, and if the user is found, create a work log on behalf of that user.
You can also configure other ways to find corresponding users on the system (by full name, by username or any other arbitrary logic that you might have).
For example, we are sharing the worklogs only in one direction, from A to B:
Add the code provided below to the Data Filter to send worklogs to the Destination side
Syncing worklogs from Jira Cloud to Jira Server
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.
Add the code below to the Create Processor and Change Processor to add/update received worklogs from the source side.
- If you sync between Jira Server instances
If you sync from Jira Server to Jira Cloud
If you sync from Jira Cloud to Jira Server
if you sync from Jira Cloud to Jira Cloud
Worklog author user mapping
You can look up the worklog author and set the author of the worklog on the Destination side due to the mapping, configured in the Create/Change Processor.
Ways to map a worklog author:
- set the original worklog author if the mapped user is not found on the Destination side
- set a default worklog author if the originally mapped user is not found on the Destination side