I think open-source organization need "hour estimated" as field, because it's the prime critieria for choosing an issue to do for yourself.
Let me explain myself a bit more :
When we work severals developpers, may be severals country, may be different hours of working, and probably different duration to spend on open-project like coworkers.
Before coworking, you have to choose a task to do from the advanced issue list and
then, you can estimate for yourself, how much time you want spend ?
Let's use http://teamfrancetriple.codeplex.com/workitem/list/advanced as example.
The project teamfrancetriple got 65 issues today (25/8/2012) and 4 developers active on their local machine and 1 with check-in by issue.
HOURS ESTIMATED field is the organization key need nowaday on my point of view.
I don't suceed in using "custom" field in that purpose because you have to open issues one by one for choosing one of it by seting status on active.
It possible but really painful.
Asked Suggestions :
a1) I'd like to have minimum and maximum "time to spend" as a criteria matching "hour estimated" field.
a2) Proposed Filtering Values :
minimum 2 hours, 4 hours, 6 hours, 8 hours, 10, hours, 12 hours, 20 hours, (maximum) 1 days
a3) Proposed business rules :
two simple rules about minimum and maximum
1) If you had less than 2 hours to spend it doesn t need an issue : just do it !.
2) If the issue is more than 24 hours you have to explain it more and split it to severals linked issue.
so it's linked after a2.
b) Add the "hour estimated" field on the result grid with sorting enable.
Some humour : I don't hope it for tomorrow -:)
I'd just like some words bellow about that.