A forum for technical support discussion related to Fogbugz.
In using FB for feature management, we have a high level feature "Phsyical Inventory": that will need to be broken into a set of 5-15 detailed features for development planning and execution.
What have you found is the most effective way to keep the set of detailed features associated with the high level feature within FB?
I handle this issue by having my larger task in FogBugz with an estimate until it comes time to perform the task.
Once it's time to perform the task, I create the individual, smaller cases with time estimates and close the over-arching case. The sum of their estimates is generally the same as the estimate of the larger case. I charge time worked ONLY to the shorter-duration cases.
This enables EBS to try to do its thing with the larger case until it's time for me to use the specific, short-duration cases. Once the large case is closed and the shorter cases are created, EBS still sees the same amount of outstanding work to be done and runs its estimates accordingly.
The only thing I'm not sure about, is how the over-arching case, when suddenly closed with an estimate present and 0 time charged to it, affects EBS, if at all.
This topic is archived. No further replies will be accepted.Other recent topics