Worklog sync had three faults, all of them quiet.
Entries could be duplicated. If Jira accepted a worklog but the reply was lost on the way back, Time Trakkr never learned the worklog existed — and the next save created a second one. The issue then showed twice the time, and nothing anywhere said so. Every worklog Time Trakkr creates is now marked, so a retry finds what it already sent instead of sending it again.
Edits made in Jira could be overwritten. If somebody corrected a worklog in Jira and the entry was later edited here, our version simply replaced theirs. Sync now checks whether the worklog changed in Jira first, and stops rather than discarding somebody's correction. Approved and invoiced entries are never altered to match an upstream change either.
Failures were invisible. A sync that failed left no trace you could see: the entry saved, which was true, and nothing said Jira had not received it.
Every entry headed for Jira now says on the timesheet whether Jira got it — In Jira, Sending to Jira, Not in Jira, Changed in Jira, or Jira not connected — with Jira's own reason on hover, such as "you do not have permission to log work on this issue". Entries that were never going to Jira say nothing at all, so the status only appears where it means something.
A failed entry has a Retry. Two states deliberately do not:
- Changed in Jira means somebody edited the worklog in Jira after we wrote it. Re-sending would overwrite their change, which is the thing we stopped to avoid — so open the issue and decide which version is right. Editing the entry here syncs it again.
- Jira not connected is not a failure of the entry, and retrying fails identically. Reconnecting is the fix, and only that person can do it, so the link appears on your own timesheet rather than a colleague's.
Worklog push is on by default for new projects. It used to be off, and the cost landed on whoever set the integration up: the mapping rule resolved, the issue linked, the hours recorded — and nothing reached Jira, because a separate per-project switch nobody had mentioned was off. Linking an entry to a Jira issue is somebody saying what they want.
Existing projects keep their current setting. Turning it on for one is a deliberate choice, because it starts writing worklogs into your Jira from then on. Workspaces that do not use Jira see nothing either way — an entry with no Jira issue is never considered for syncing.
One date bug went with it: worklogs were sent as midday UTC, which is the following day in New Zealand and anywhere else past UTC+12. Time logged on a Wednesday arrived in Jira on Thursday. It now uses midday in your own timezone, worked out for the day the time was logged, so a backdated entry across a daylight-saving change lands on the right day too.
The remaining estimate
There is a new workspace setting for whether logging time reduces the issue's remaining estimate. It is off by default: reducing an estimate somebody else set is a change to their planning, not ours to make uninvited. Turn it on and Jira's burn-down starts tracking reality.