Yes, I figured that out. But the problem is that there are literally hundreds if not thousands of pointless signatures enabled after setting things up with broad brushstrokes. I tried to make it as granular as possible with classtypes and categories but still there's huge amount of stuff enabled that is completely pointless as well as stuff that is not enabled but should be.
Picking these signatures out one by one into separate rule(s) would be a lot of work. With the old system I could just go through the list and check/uncheck what is needed. It would take a day or two to go through the list but in the end only necessary signatures would be there.
With the current system it will probably take a week, probably more to pick all the signatures out into a separate rules. For example, about 2/3 of the signatures in web-attacks are completely useless because we do not have these web apps but there's no way to narrow the selection even more down sans manually copy and pasting every signature id into a separate rule set. That's crazy. It will create a huge mess.
I do appreciate the ability to mass enable the signatures but the new system is far from perfect. A simple ctrl/shift + click action would have been much better. As the list can be sorted by signature comment, protocol etc all that was needed was an ability to mass select a block of signature and enable/disable them.