Add option to group build issues (by type, by folder, etc.)

Problem: Sometimes a lot of warnings about a specific issue can spam the build issues dialog.
One solution to this is to fix the code so that the warnings are not issued, but that solution is not always possible (if the code is imported from another project, for example).
Another solution is to turn off that warning with a compiler flag, but that is also not always desirable, because some instances of the issue may be worth attending to.
This happens to me a lot in that a project on which I rely contains source code that consistently uses a style that generates a lot of warnings on my compiler, and thus every clean build I need to sift through lots of repetitions of the same warning to see if there are any that I need to pay attention to.
Possible solutions:
If I could group build issues by type, then for example I could collapse all the "allocates zero-length array" warnings under one heading, and attend only to other warnings.
Instead, if I could group build issues by which folder the source file is in, then for example I could collapse all the warnings for src/someSubFolder/ files and attend only to the others.
An alternative to this latter approach would be to put badges on the files in the project tree view to point out where warnings happened in those files, and clicking the badge would, like a hyperlink, jump to the first warning/error in that file. If there were a "next build issue in this file" command to which one could assign a hotkey, it would then be easy to navigate just the build issues in the files I'm in charge of.