I'd agree with this. Our previous Scheduling vendor before we found this AWESOME product, was Tidal Enterprise Scheduler which apparently is now owned by Cisco. It had an option to create any number of groups for filtering and it's one of the few features Tidal had that I actually miss.
So I might have a job that is VBscript and does a reboot of a server, or a file transfer using NDM (Connect:Direct), etc..
I could have a group for VBScript. A Group for 'Server Reboot'. And a Group for 'NDM Submission'. A job might be in any number of those groups, but it'd be nice to, at a glance, know every job that uses NDM. Or, Every job that can/will involve a reboot.
Brian