We started doing time estimates in days, figuring that one day is worth eight hours of work. But we discovered that if, for instance, you estimate that a task will take 1 day, and then log 4 hours, it says you have 20 hours of work remaining. Who works 24 hours a day?

So, we decided to ignore days, and work strictly in hours. By now, we had realized that 6 hours of actual programming time per day is more realistic than 8. So, instead of estimating that a task would take 2 days, we said it would take 12 hours. So far, so good. But then we entered a large task which we estimated would take 30 hours (5 days). The next time we looked at the issue, it had a time estimate of 1 day, 6 hours.

Our next try is to start using minutes to track hours, since we can go up to 60 before it starts recalculating on us. But now when we make printouts or link with other project teams, it looks like we have a whole bunch of tasks that we're expecting to finish in 6 minutes each.

Ideally, it would be nice to be able to configure how many hours are in an ideal work day. It would suffice to be able to turn off the units and work with raw numbers.

Thanks.