Knowledge Base Articles
Knowledge Base Articles
Breadcrumbs

Tempo and Jira worklog sync on Cloud

This article is for Tempo for Cloud only.


As Tempo host Tempo data outside of Jira instance, there are many ways to sync Tempo data into Jira and vice versa. The near-real-time webhook sync is the expected/default behavior for worklogs created via UI or API in either Tempo or Jira. Daily-sync-instead-of-webhook (Jira Import, JCMA, CSV import) and many-to-one aggregation (when internal-item summary worklogs are enabled) are exceptions with specific triggers, not alternate "normal" paths.

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. Moving worklogs with Jira API

When worklogs are moved using the Jira API, Jira creates a new worklog in the target issue and deletes the original worklog from the source issue.

However, if those worklogs were originally created via Tempo, moving them through the Jira API causes two main issues:

  1. The worklogs are moved without an Author or Description.

  2. Jira does not notify Tempo about the deletion, leaving duplicate "ghost" worklogs behind on the Tempo side.

There is no way to sync these worklogs.

To prevent these discrepancies, Tempo strongly recommends using the Tempo UI to move worklogs rather than the Jira API.

F. Summary Worklogs for internal issues

For instance, with summary worklogs enabled, there is no longer a 1-to-1 worklog between Jira and Tempo. Therefore, the worklog sync only happens around midnight as per your instance’s time zone setting, with 1 worklog per day to work with Jira 10k worklog limitation.

G. Manual Sync

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