Basically, I cannot select multiple rsids and edit SAINT classifications for xyz variable unless the classifications for xyz variable are the same for all the selected rsids.  This makes it really hard to change classifications across rsids, especially since there's no easy way to tell which rsids d...

also sometimes it shows up cutoff.  Dunno if it is because of position on page or with certain browsers (I've seen it in FF and Chrome).  I have to click save again in order for the popup to fully appear.

DataWarehouse will let you do a regularly scheduled export to an ftp or email location.  It's not as convenient as being able to schedule a recurring export from SAINT (main thing is that it doesn't include the template header, so you'll have to get that separately and keep it up-to-date), but it's ...

If you allowed for regex matching instead of a single * wildcard, 50 might be enough.  But usually there are a list of ranges that need to be exluded like 1.2.3.[1-9] and currently I have to either burn 9 slots or else exclude 1.2.3.* and filter out more than I want.  

YES.  Sometimes it has taken upwards of a WEEK for classifications to be processed. 

I agree with the other posters here.. we work with several clients that are quite large.  Hundreds of report suites dedicated to specific sites, markets, countries, regions, etc.  Keeping things consistent all the way up to the global rollup is a daunting task.  A lot of it boils down to red tape.  ...

Even more better yet, allow us to edit VISTA rules... come on, you let us get our feet wet with processing rules, but processing rules are so limited they are rarely worth it. 

This is one of those things that sounds like a good idea on paper but in reality, may cause more harm than good.  I would not recommend allowing new code to be introduced directly to production environments, and allowing for updates to core code to be automatic will do just that.