We use an internal system for booking hours spent. I know FogBugz can do this but we have good reasons. I'll spare you the details :-)
For one project, our internal systems were showing a lot of hours booked against a project. However, looking at FogBugz, it didn't seem as if much progress was being made. I was looking at the Total Estimated Time Remaining at the bottom of the task list and comparing the values when filtering on All Tasks vs Active Tasks.
I traced it down to tasks that had been marked as completed, but for which FogBugz still has several hours left under Remaining Time. To me, this seems misleading. If FogBugz makes it seem like there are 150 hours still left to go but my internal systems say there's only enough budget for 100 hours and I start to make contingency plans, only to find that FogBugz actually knows that 50 of those hours are tied up in the remaining time for closed tasks then I'd have spent time on contingency plans / actions that weren't needed.
I'm still fairly new to FogBugz. Am I looking at the "wrong" figures?
One option would be to try to persuade developers to update Current Estimate to match Time Elapsed when they close a task, but this is compounded by the fact that FogBugz uses Current Estimate rather than Elapsed Time + Current Estimate of Time Remaining (which, in my experience, is much closer to how developers actually think and work) but there's already a question about this [here][1].
Any suggestions?
