Ask HN: QA Cascade?

How do you guys handle a case during the quality assurance phase of a project, where one bug cascades into many issues? For example, a Javascript error that causes several functions around it not to run, thus breaking several features?

There's no good way for QA to know that they're all from the same root cause, so we end up losing a lot of time to the administrative overhead of say, 5 tickets, when as a developer I know it should only be one?