Tempo and Jira worklog sync on Cloud

As Tempo host Tempo data outside of Jira instance, there are many ways to sync Tempo data into Jira and vice versa.

A. Create worklogs in UI

1. Worklogs created in Tempo, Tempo automatically update Jira instance with basic worklog info.

2. Worklogs created in Jira, Tempo automatically syncs Jira worklogs over to Tempo instance through listening to Jira webhooks.

B. Jira Import

For Jira worklogs imported through Jira Import, no webhooks are sent. The worklogs are therefore not synced on import. Tempo daily checks and syncs these Jira worklogs without webhooks.

C. Create worklogs with REST API

1. Create worklogs with Tempo REST API, Tempo automatically updates the Jira instance with basic worklog info.

2. Create worklogs with Jira REST API, Tempo automatically syncs Jira worklogs over to the Tempo database through listening to Jira webhooks.

D. JCMA

For Jira worklogs imported through JCMA (Server to Cloud Migration), the Tempo instance has daily sync for these Jira worklogs without webhooks.

E. Manual Sync

Last, should you find any missing worklogs in either Jira or Tempo instance, you can always contact Tempo Support for manual sync.

F. New Worklog Sync

Starting from November 2022, new worklog sync is a continuous process, not an hourly sync like before, which creates more even distribution of request load to handle large tenant better by limiting the amount of synced worklogs per iteration to 100K worklogs. It divides the sync-workers more equally between tenants, large syncs (such as Server to Cloud Migration) don’t block smaller syncs, and request load is more distributed.

Starting from March 2023, worklog sync still is a continuous process, but switching to an asynchronous approach to reduce latency of the endpoint by a significant amount and to improve latency when creating worklogs using the public API.