When you enter an item into a FBz project, the report does not account any hours against that task because it has not been estimated. In our process we would like to use a 3 hour default sizing for the tasks that are entered. This will allow us to see a realistic picture of the current effort rather than ignoring un-estimated tasks. One approach is to use a plugin to set the 3 hour estimate on every bug that is entered but this makes it harder to track which items are sized or not. Is there a way to allow FBz reports to assign default estimates?
|
1
1
|
|
|||
|
|
|
1
|
I suggest voting for this request: http://fogbugz.stackexchange.com/questions/1268/feature-request-an-option-to-tell-ebs-to-take-unestimated-cases-into-account |
||
|
|
|
0
|
There isn't a way to set default estimates because this would throw a wrench in the way EBS works. EBS uses historical data of each user's estimates vs actual time to determine how to treat their estimates in the future. e.g. if Bob always estimates his cases at twice what it takes to finish them (because he's very conservative), when he enters new estimates, EBS knows to halve them when predicting the ship date for the project. If default estimates were put in, they would need to be by a user. Whichever user that was would likely end up being completely untrustworthy in the eyes of EBS because the actual times for all the cases would look random compared to the constant 3 hour estimates. To predict ship dates / work remaining accurately, it really is best to make sure to estimate all the cases you are including in a release / milestone. You should also make sure that the developer who is going to work on the case is the one who estimates, to maximize accuracy. Here is a good article on EBS 1.0 by Joel and a blog post by our EBS guru about the latest version (2.0) |
||
|
|
