A fix for time lost during simultaneous saves, and a form that resets after every entry

Version 2.0.42 · All release notes

We’ve published a new update to the Time Log extension for Azure DevOps. The headline is an important fix for logged time going missing from a work item’s Completed and Remaining fields when two saves overlapped — alongside a nicer everyday experience: the form now resets ready for your next entry after each Add, and a date picker fix for some long-standing organisations. There’s nothing you need to do — here’s what changed.

At a glance

• 🛡️ Fixed: time lost when two saves overlapped — Completed and Remaining now always reflect every entry
• ✨ The form resets after every Add — cleared and ready for your next entry
• 📅 Fixed: date picker refusing every date — on organisations set up before the lock-date option existed

🛡️ Fixed: time lost when two saves overlapped

Fixed in v2.0.42

If two time log entries were saved against the same work item at nearly the same moment — a double-click on Add, the same work item open in two browser tabs, or two people logging at once — one entry’s time could silently go missing from the work item’s Completed and Remaining fields. Both entries were recorded (sometimes looking like duplicates on the same day), but the work item’s totals came up short. This happened because each save read the work item’s current value, added its own time and wrote the result back — so two overlapping saves both started from the same value, and one overwrote the other.

Two safeguards now close this:

• The Add / Update buttons are disabled while a save is in flight — on the work item’s Time Log tab and in the My Time Log dialogs — with the saving spinner now shown for the whole operation, including the work item update. A double-click can no longer fire two overlapping saves.
• Updates from My Time Log are now checked against the work item’s revision: a write based on an out-of-date read is rejected by Azure DevOps, recalculated from a fresh read and retried automatically. Simultaneous saves from other tabs or other users are merged instead of overwritten.

Nothing changes in how you log time — the totals are simply always right.

✨ The form resets after every Add

After adding an entry on the work item’s Time Log tab, the form now resets ready for the next one: Hours, Minutes and Comment are cleared, the Date returns to today and the Type returns to your default time type. Previously everything except the comment carried over from the last entry, which made it easy to log time accidentally against yesterday’s date or the wrong type.

Two sensible exceptions: if a save fails, everything you entered is kept so you can try again, and a multi-user selection is preserved so you can log another entry for the same group straight away. The default type is also now taken from the work item’s own project, so it’s always the right default even when you’re browsing from another project.

📅 Fixed: date picker refusing every date

Fixed in v2.0.42

On organisations whose Time Log configuration was saved before the lock-date setting existed, the date picker could refuse every date, making it impossible to log time at all. This is now fixed — if you’d run into it, logging works again with this update, with nothing to reconfigure.

Full change list

2.0.42

Time Log: fix logged time going missing from the work item’s Completed / Remaining fields when two entries were saved at nearly the same moment — for example double-clicking Add, or logging to the same work item from two tabs or by two users at once. Each save read the work item’s Completed value, added its own entry’s time and wrote the result back, so overlapping saves both started from the same value and one increment was silently overwritten: both time log entries were recorded (appearing as duplicates on the same day with the same type), but the work item’s Completed came up short of the entries’ total. Two guards now close this. The Add / Update buttons — on the work item’s Time Log tab and in the My Time Log dialogs — are disabled while a save is in flight — with the save spinner now shown for the whole operation, including edits and the work item update, rather than only the initial request — and a repeated submission is ignored, so a double-click can no longer fire two overlapping saves. And the My Time Log update path now stamps each write with the work item revision it was calculated from, so Azure DevOps rejects a write based on a stale read; the update is then recalculated from a fresh read and retried, meaning simultaneous updates from other tabs or users are merged instead of overwritten. Time Log: after Add, the form now resets ready for the next entry — Hours, Minutes and Comment are cleared, the Date returns to today and the Type to the default time type (previously everything except the comment carried over). A failed save keeps what was entered, and a multi-user selection is kept so the same group can be logged for again. The default type now comes from the work item’s own project rather than the page’s current project. Also fix the date picker refusing every date on organisations whose saved configuration pre-dates the lock-date setting.