Knowledge Base Articles
Knowledge Base Articles
Breadcrumbs

Tempo vs Jira Worklog Discrepancy Check (Cloud)

This article is for Tempo for Cloud.

Purpose

Use this checklist when worklog hours in Jira don't match what customers or internal users see in Tempo (reports, timesheets, worklog list, or the Tempo panel). Work through the steps in order: most mismatches are visibility or sync-timing issues, not data loss.

Quick triage

Symptom

Likely cause

Next step

Jira shows hours on the work item, but Tempo worklogs or details are missing. The Tempo total may still look right.

Permissions. The user can't see other people's worklogs.

Step 1

Worklog exists in Jira but not in Tempo.

Sync gap or interrupted sync, or a migration sync to Cloud that hasn't completed.

Step 2

Changes made in Jira to a Tempo-created worklog don't show in Tempo.

Expected one-way behavior. Tempo-originating worklogs ignore Jira edits.

Step 3

Counts differ between Jira and Tempo reports.

Summary worklogs sync around midnight, or the worklog was created or deleted on one side only.

Step 4

Step 1: Check visibility and permissions

Users see other people's worklogs in Tempo only with the right permissions: View All Worklogs and View Issue Hours on the space, or View Worklogs on the Tempo team. Confirm the viewer's role first. See Worklog of users not visible.

Step 2: Confirm a missing worklog and attempt a re-sync

  1. Open the work item's Jira audit history for the worklog. If it shows the worklog was created and synced with no deletion, a service disruption may have interrupted the sync.

  2. Ask a Jira admin to make a small edit to each affected worklog (for example, its comment). The edit triggers a sync from Jira to Tempo.

  3. Check that the worklog now appears in Tempo. If Tempo-only data such as work attributes is missing, set those values again in Tempo.

  4. If it still doesn't appear, contact Tempo Support with the issue key and the Jira worklog ID.

After a migration to Cloud, if worklogs appear in Jira but not Tempo, the sync usually hasn't completed. Support must trigger it, so send a few example issues. See Syncing Data Between Jira and Tempo failure.

Step 3: Understand one-way sync for edits and deletes

Updates or deletes made to a worklog that originated in Tempo are reflected in Jira. Changes made in Jira to that worklog are ignored in Tempo. This can make Jira and Tempo counts differ. To track changes, use the Tempo API to search for new worklogs, or subscribe to worklog events with Tempo webhooks. Reference: apidocs.tempo.io.

Step 4: Check sync timing

  • Worklogs created in Tempo or Jira (UI or API) normally sync in near real time through webhooks.

  • Summary worklogs sync only around midnight in the instance time zone, with one worklog per day, to stay within Jira's 10k worklog limit. Expect a delay.

  • For persistent gaps, Tempo Support can run a manual sync. See Tempo and Jira worklog sync on Cloud.

Step 5: Use the audit log

Before escalating, check the Tempo audit log for the worklog's create, update, and delete history. See Worklogs Seem Missing or Don't Match Reports (Understanding the Tempo Audit Log). If the worklog was created through the Jira MCP connector and has no work attributes, see Missing Mandatory Work Attributes in Worklogs Created via Jira MCP.

Escalation template (send to Tempo Support)

  • Issue keys where hours differ

  • Which side is missing the worklog (Jira or Tempo), with the Jira worklog ID if known

  • How the discrepancy was found (report, timesheet, worklog list, or panel)

  • Side-by-side screenshots of the Tempo and Jira values

  • Whether a migration to Cloud happened recently

  • Steps already tried from this page