New

A worklog changed in Jira now says so here, instead of nothing happening

If somebody edits or deletes a worklog in Jira, the linked entry now tells you — without overwriting your hours or removing your time.

Time recorded here flows to Jira. Until now, nothing came back the other way: if a colleague corrected your worklog in Jira, or deleted it outright, the entry in Time Trakkr carried on as though nothing had happened, and the two quietly disagreed for good.

Time Trakkr now checks Jira's own record of what changed, once an hour, and says what it found.

An edit in Jira flags the entry, it does not overwrite it. The entry is marked Changed in Jira and your hours are left exactly as you recorded them. This is deliberate. Somebody editing a worklog in Jira has not asked us to rewrite your timesheet, and an integration that silently changed hours you had already reported would be worse than one that stayed quiet — you would have no way of knowing a number had moved. The flag is the point: it tells you the two sides disagree and lets you decide which is right.

A worklog deleted in Jira unlinks the entry and keeps the time. The Jira link is cleared and the entry says why, but the hours stay. Deleting recorded time because Jira lost a row is not a decision an integration gets to make, and the hours may well have been real.

An entry that is approved or invoiced is never touched. It becomes a conflict with an explanation instead. Those hours have been signed off or billed, and changing them behind the approval is the one outcome nobody wants.

Nothing here is retroactive — the check looks forward from the point it was switched on, not back over every worklog that ever existed.

← Everything that has changed

The hours, the invoices, and what they earned

Free for unlimited people. One paid plan, $10 per member per month, when you want HR, scheduling, timesheet approvals, scheduled backups, email from your own domain and scheduled reports.

Start free