STR:
1. If you move a task from Not Started to Complete without logging any time, the time spent will default to .1 and hours will default to 0 for the progress bar.

2. If you create a task on a story slideout and start it as complete it will allow you to spend 0 time on task and hours will remain as inputted for the progress bar.

This functionality leads to issues with % complete on the progress bar, as all tasks can be completed but the progress will show as a low percentage complete.

there appears to be an automated time tracker on each task that’s entering time for us.  Since we’re sucking at moving tasks to the correct status, then moving a bunch all at once.  It appears that it puts an arbitrary .1 hours on “Time Entered” of the task since we move it from Not Started to In Progress then Complete within a couple of minutes time.

See screenshots

See the progress bar pop-up when looking at our Team Room / Dashboard.  It says the story is 12% done because of this time entered is putting .1 hours on each task.  Even though all tasks are now done.

ER:
AgileCraft should no longer apply an arbitrary .1 hours spent on task completion
When users go to close a task, if there are Hours (estimated/remaining on the task not equal to 0) the user should be forced to enter a number of hours spent. Remaining will still update to 0 (since the task is done)
This should apply to the dropdown state change AND drag and drop (Team Room and Kanban Boards - when the state is mapped to columns).

Connectors:
Mark the task as done and assume the hours are done - we should not apply any arbitrary time spent with connectors
If a task has 10 estimated hours and a task comes in as done (from the connector) we should assume all 10 were burned (from a report perspective)

AR: completing tasks adds .1 hours