Worklogs Seem Missing or Don't Match Reports (Understanding the Tempo Audit Log)

Problem

If a team member reports that logged hours have disappeared, or if timesheet reports (such as Planned vs. Actual or Timesheet Reports) appear inconsistent with the Tempo Audit Log, the worklogs are usually not missing.

This confusion typically stems from how the Audit Log indexes events:

• The filter bar queries by Action Date (when the worklog was created, updated, or deleted).

• The row details display the Work Date (startDate) (the actual day the hours were logged for).

Symptoms / Common Scenarios

• An employee reports their hours were "wiped out" or "deleted" for a past period.

• The Planned vs. Actual report shows logged hours, but filtering the Audit Log for those same dates returns zero results.

• An employee logged hours retroactively in bulk, causing date discrepancies between reporting views and log queries.

• You need proof of when an entry was submitted, edited, or deleted.

Root Cause: Filter Date vs. startDate (Work Date)

The main date picker in the Tempo Audit Log filters strictly by the timestamp of the action, not the day the work took place.

Key Rule: If you set the Audit Log date filter to Sept 19 – Sept 30, it will only show actions performed during those days. If retroactive entries for September were logged in October, they will only appear when filtering for October.

Solution

How to Investigate "Missing" Worklogs

1. Broaden the Audit Log Date Filter

• Avoid filtering solely by the dates the user was supposed to have worked.

• Set the filter range to cover when the user likely performed the action (e.g., the current week, month-end submission periods, or the full preceding month).

• Filter by User or Issue Key to isolate all activity for that person.

2. Expand the Audit Log Entry to Check startDate

• Locate the relevant event row (e.g., WORKLOG_CREATED, WORKLOG_UPDATED, or WORKLOG_DELETED).

• Click the row or expand arrow to view the event payload and metadata.

• Look for the startDate attribute:

  • startDate confirms the exact date the hours were applied to on the user's timesheet.

  • This confirms whether a worklog exists for the date in question, even if it was created weeks later.

3. Review the Specific Action Types

• WORKLOG_CREATED: Confirms initial submission. Expanding this reveals the original startDate, duration, and issue.

• WORKLOG_UPDATED: Highlights changes made after submission, such as modified hours or shifted dates.

• WORKLOG_DELETED: Confirms if hours were actually removed, along with the timestamp of deletion and who removed them.

Still Can't Locate the Worklogs?

If the Audit Log shows no matching WORKLOG_CREATED event even across an expanded date range:

1. Submission Failure: The entry may not have successfully synced or saved (e.g., closing the tab prior to submission, network timeout).

2. Account Discrepancy: The time may have been logged under a secondary user profile or an incorrect issue key.

3. Escalation: If you suspect an integration failure or data loss, contact your Tempo Administrator or Tempo Support with:

   • User's Display Name / Account ID

   • Issue Key(s)

   • Target Work Date (startDate) and hours reported missing