By product grouping would be nice but currently the biggest issue is now the default behaviour of denying a patch if it is both approved and denied in two different collections. Effectively makes having the ability to make a machine part of multiple collections redundant.
I'd love to see a response from kaseya on this.. (hint hint..)
Even if it's not an offical "notice" just some indication that they feel our pain would be nice.
This feature request is not possible because the Microsoft Update Catalog is update-centric and not product-centric. While we can identify a general product (e.g., Windows XP vs SQL Server 2005) for a specific machine, the actual patch can apply to multiple products (e.g., Windows XP, Windows 2003, etc.). Therefore, the patch data does not have any product identifiers. This prevents us from grouping by product. The one exception is the ability to identify updates for Office vs. non-Office. Because the Office patch data comes from a different data source (Office Detection Tool rather than the Microsoft Update Catalog), we know they are Office patches and which general version (2000, XP, 2003, 2007). So, we are looking into making a change in an upcoming release to somehow distinguish/filter on Office updates. The change has not neen designed yet, so there is no detailed information about how we will accomplish this.