Schneecrash writes "Submitting bug reports — and waiting for responses etc. — seems to be SOP for developers and users alike, these days. Every project has some sort of bug-tracker — bugzilla, trac, mailing list, etc. E.g., we currently track 200+ outward bugs across ~40 OSS projects. Half the bugs depend on article else getting fixed, first. Every bug has its own email thread, etc. supervision asks 'How we doin' overall?,' and abruptly everyone tangled gets to work removing dried gum from the bottom of their shoe. What do Slashdotters use/recommend for centrally keeping track of all the bugs you track across all those originative bugtrackers? In particular, managing communications and dependencies across bugs? So far, the best method I've managed to use is bunches of PostIt-notes stuck to the screen of an out-of-commission 32" TV (glossy, non-matte screen, of course!)."

Read more of this story at Slashdot.

More: - Brought to my attention by

Mark