Fix

An entry that said "sending to Jira" is now actually being sent

The hourly check could leave an entry marked as syncing to Jira without anything behind it, so it stayed that way. It now queues the work first and only marks the entry once it has.

The hourly check that compares your timesheet against Jira has a case for entries where your copy is the authoritative one and the Jira worklog has not been touched: send ours across. It marked the entry Sending to Jira and then did not queue anything, so the entry sat in that state indefinitely — reporting work in progress that nothing was doing.

Nothing was lost and nothing in Jira was wrong; the entry simply stopped describing reality, and because the broken version looked busy rather than failed, it raised nothing. Two entries in our own staging workspace had been stuck that way since 11 September.

The check now queues the sync first and marks the entry only once that has succeeded — and if the queue cannot be reached, it leaves the entry alone rather than promising a sync that will not happen. It shares the same grouping window as saving an entry does, so a save and an hourly check landing together produce one sync rather than two.

← 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