FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at

Posts by Fog Creek Employees are marked:

Release Notes
Network Status

EBS and Case types

I've seen this topic brought up here before, namely whether EBS will calculate differently based on the category - features are easier to estimate than bugs, etc, and keep separate histories accordingly. 
I've also seen the common response - not yet decided, but anyway bugs happen so why not just let EBS handle the probabilities? 

I wanted to bring up another more subtle issue around this - a developer might be able to properly estimate coding time, but when tasked with documentation - his estimates only connect with reality coincidentally. Or maybe a Web developer was given an installation script to build, and she had no idea what this involves - and thus estimates completely different from how she usually does.

This type of thing would throw EBS completely out of whack, especially since given the type of task, EBS should be able to have better info...

Perhaps this could be based on Area, and tracking history kept separate per Area? (This suggestion based on common FB documentation, to use Areas for things like Documentation, Installation, Front end, etc.)
Or maybe a new field, like "Tags"? (though I think that would start to get too complex, and I'm not sure I would like that part...)
Avi Douglen Send private email
Thursday, February 19, 2009
Who is going to be writing the docs?  You could just have them estimate the documentation cases.
Michael H. Pryor Send private email
Friday, February 20, 2009
I think you misunderstood me, The same developer would be writing the docs himself.
Unfortunately, in many a small company, everyone wears several hats - better at some, slower at others. For instance, a programmer may have to write the documentation, and since he IS a programmer (and not a tech writer) he has no idea how long it will take him - hence his estimates are completely wrong wrt to HIS work on documentation, even though he might be very good at estimating his coding time. Or maybe she's a brilliant network developer, but has to also upkeep the company's website (including HTML/CSS) - a newbie at UI....
My point is, sometimes we're good in one area but suck at another - but still have to do it anyway...
Avi Douglen Send private email
Saturday, February 28, 2009

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.