v2spa is AWESOME for finding large groups of related alerts, and ensuring that I can take new alerts and group them in with ones the dashboard would have auto-grouped after the bug has already been filed.

But when you need to pull an alert into a new bug, it seems that v2spa keeps that alert in the same group. An example is https://chromeperf.appspot.com/group_report?bug_id=896254

It was hopefully just user error that caused me to somehow group system_health memory benchmarks with system_health common benchmarks with a bug that's about rendering benchmarks. But now I split the system health alerts into new bugs, and they still show up in the original group in v2spa. Dozens of new alerts come in, and the easiest thing to do is select all -> existing bug. This re-triages the system health alerts into the original bug, ensuring that I make the same mistake over and over again.

So two issues here:
1) It'd be great if there were a way to only select the untriaged alerts in a group. This would prevent the re-triaging, and also speed things up--adding 10 new alerts to a group of 500 is a common task, and triaging is O(N).
2) It'd be great if the dashboard didn't group things together that are unrelated. Another example is this screenshot: why is the highlighted row in the group? It's a different benchmark, a different metric, and triaged differently.
 

Deleted: grouping-problem.PNG 50.9 KB

	grouping-problem.PNG 50.9 KB View Download