Misleading / Unhelpful behavior when filtering Alerts belonging to alert groups

Imagine you have an alert group containing 10 alerts for 5 different resources, one of which (WNPGMBAB-14) has 5 different alerts, with 1 Critical, 2 Major and 7 Warning severities.
The Alerts page will show the Group with "GROUP (10 alerts) ..." at the top and all the individual alerts listed once you open the ">" next to the group.

If I set up a filter that matches only some of the alerts (e.g. Severity Major or Resource WNPGMBAB-14) the list changes to "GROUP (2 alerts) ..." or "Group (5 alerts) ...", and only the matching alerts are shown below the group.

There doesn't seem to be any way to know that the group is actually larger (it has 8, not 2 or 5). And there is no way to see the other alerts in the group.

So if I run a filter to find "interesting" alarms, and then I want to see what else is in the group I have to:
- run the filter.
- remember the alert group summary and its firstOccurrence time
- clear the filter so that all the alerts are showing
- sort the list by firstOccurrence
- scroll to the right time
- use the alert summary to find the right group

Except that when I try this I can never seem to find the right group.

I would prefer that if a single alert within a group matches, that the ENTIRE group be shown in the filtered results (or maybe there is an option to "show all alerts within matching groups". 

In any case the group summary should NOT change the number of alerts, so that even if a single alert matches, the group summary should still be "GROUP (10 alerts) ..." to let you know that there are more alerts.

This current behavior is making it VERY difficult to debug our alert grouping rules, since we can't reliably determine what alerts are in the group.