I think this is a symptom of a deeper issue: a bug search listing should collapse all matching tasks into one row per bug, with the relevant data for each task being shown in that row.
The confusion is equally apparent in, for example, the +subscribedbugs report.
I think this is a symptom of a deeper issue: a bug search listing should collapse all matching tasks into one row per bug, with the relevant data for each task being shown in that row.
The confusion is equally apparent in, for example, the +subscribedbugs report.