Time Estimating

The project time estimate fields needs to be updated. Right now, there is no concept of units on the field.

I would use it probably as ideal days—which I would term as 8 hours per day.

I'd be interested in some input on how others have used the field, or what they think should go there.

I perceived the project level estimates to represent days while the issue level estimates are clearly hours and minutes. I am just not certain how these will translate into estimated vs. actual on reports. Or how comparisons will be handled in roll-ups.

There is also a limitation with project level estimates. The maximum number the spinner will allow is 80. This effectively constrains project estimates to 80 days. I have project plans that span 12–18 months.

Perhaps all estimates should be stored internally as minutes. Then a standard input format used for entering estimates (e.g. 12M:3d:4h:35m). Output format can vary depending on the rendition format. I'm just thinking out loud here.

I use time estimate like points. time estimate is hard for me and I'm pretty inaccurate when it comes down to it.

http://ornus.planningpoker.com/detail.html

actually, wrong link:) it's an article explaining points:
http://www.planningpoker.com/detail.html