[Defect] time tracking is lost between years or iterations

Status: [ ] Works As Designed Complete: [Complete] Complete
Importance: [Critical] Critical Urgency: [ ]  
Severity: [Minor] Minor Frequency: [Frequent] Frequent
Release: [Release] v1.2.0

Description

moving into 2007 I was surprised that AgileTrack didn't show time spent on the task previous year. when I open Issue/Time it shows all time spans, but in all other views it doesn't count it. only new time.

I'm assuming that total time gets reset on new year. another possibility is that it gets reset when issue changes iteration (i.e. I didn't finish it in 1st iteration, so I moved it to the 2nd), but it used to remember total time fine between different iterations.
Issues

Comments

Time tracking and time estimates need to be reconsidered a bit. The original thinking was that an issue's time estimate would also be reset when the issue was assigned to an iteration. Since the time estimate would be reset, it seemed appropriate to have the time logged be limited to the iteration as well. The time that is shown for an issue in the issue lists will be the time logged during the iteration that the issue is currently assigned to. If the issue is not assigned to an iteration, it should show its total time. Once the issue is completed it will also show the total time. This isn't very intuitive. The time shown in the table is blue if it is only showing the iteration time.

—Posted by Adam Lane on Jan 27, 2007 at 10:15:25 PM


You can add comments to this issue, but you must be logged in. If you already have an account, you can login now. If you need to create an account, you may also register now.