Is there a way to express a dependency between multiple bugs. I would like to use FogBUGZ in part for our build / release manager. He would be able to see that a developer has requested that their application be released, however, releasing his application requires modifying some database schema (or any other arbitrary dependency).
You could add a note that says
Michael H. Pryor
I would love to see a more robust bug dependency feature. Our products are built on a core set of libraries that another in-house team develops, so often defects in the products are traced to defects in the core. We need to have two defects open -- one to fix the core bug and another to implement the fix (when available) in the product.
The solution that I've currently seen in our development team is people will just forward bugs around where it would really make more sense to open a seperate bug against the infrastructure component and make their bug depend on the infrastructure bug.
Fog Creek Home