Suppose regression testing reported many defects, and now we need decide about the order in which to correct them. In addition to commonly used defect prioritization based on their business importance, we propose to take into account also dependencies among defects, and to correct defects in an order that reduces the overall debugging effort. A goal here is to start by fixing root causes of failures, i.e., defects that may be causing many other program failures. A related goal is to avoid prematurely fixing defects that depend on other, yet to be fixed defects, as this is likely to incur wastage of time. Our proposed method requires that test cases have been mapped to relevant software requirements. We defined heuristics to infer defect dependencies, and a suitable defect debugging order from these mappings. The process is semi-automatic, supported by a tool called TRAcker. TRAcker accepts test results, performs heuristics-based computations, and recommends a time-efficient defect debugging order from the perspective of defect dependencies. TRAcker’s filtering and visualization features allow a user to participate in the process, so that tool recommendations as well as other factors can be taken into account. We show that defect prioritization on technical and business grounds together contribute to effective debugging.