I note that milestones can be dependent on other milestones, but I'm not exactly sure how the feature works. Can you explain?
|
2
|
|
|
|
|
1
|
Check out all the discussion and documentation around EBS - the FogBugz scheduling reports are based on probabilities. So, if a developers are assigned Cases with independent milestones, the reports will show if there's a 65% probability that they are still working on tasks in one milestone, then there's a 35% probability they are working on tasks in the other. If one milestone is dependent on another, then FogBugz takes in to account that they may be blocked... i.e. they have a certain probability of working on milestone 1, which means they could conceivably be working on milestone 2, but because of the dependency they also may be blocked. So, the reports will show a potential delay in progress if all cases in a milestone aren't predicted to complete around the same time. |
|||
|
|
