When an existing work item (Task) already has a non-zero Actual (hours) value specified directly in ADO (not Timetracker), and a subsequent work log entry is created using Timetracker the Actual value is updated to reflect ONLY the Timetracker work log total - destroying the previous Actual value.
Related - what would happen if a user's 500/1000 work log limit is reached - are only visible work log entries considered for the Actual calculation?
Expected: Actual is treated similar to Remaining where the stored value is adjusted by the work log value. Not overwritten from Timetracker log entries.
Please sign in to leave a comment.