I've got about 70 ticket filters set up right now. I love that feature. Started running into a little trouble with them last week, around Aug. 21. I think I need to start this one with a little background - We manage 20something buildings, each building has a local person that is the first line of tech support for the building. Each building also has a gradebook rep and a webmaster. For the most part each role is filled by a different person. In the past, each of these groups have had their own separate work order "system" (mostly emailed forms). Since OSTicket introduced ticket filters over the summer, we decided it was a good time to bring all these different trouble ticket systems under one roof.The way our filters are processed from order 1 down is as follows -1. Specific topics that we already know are going to need one of us are routed straight to one of us first2. School level webmasters are assigned tickets pertaining to website problems for that school3. School level gradebook reps are assigned tickets pertaining to gradebook problems for that school4. School level tech support get everything else pertaining to that schoolThe trouble we started running into last week were in steps 2 and 3 of that rundown. These are the only filters that required two rules, the best I can tell is that the it was ignoring "Match All" and instead was matching Any. Screenshot attached of one of the affected rules. What should happen (and was prior to last week), is any ticket where the user selected Opportunity Center as their site and Gradebook Problem (topic_id 36) should go to the OC gradebook rep. Was was happening instead is that is was going to the OC tech support person. You can see in the screenshot, that matching the site name was the first rule of the two in the filter. It was like it was ignoring the Match All, hitting the top rule of the filter, and just acting on that. I did make sure to check that I had Match All selected. I bumped the priority of that filter up to 1, that didn't help either.Looking more closely at the calendar, I noticed the only thing that had changed since I started getting the complaints is the fact that I had updated to 1.9.3 on Aug. 16. I keep nightly backups of the www directories and the database, in case of something like this. I rolled the www directories back to 1.9.2, the filters started working correctly again.I'm not sure if this would be better as a bug report over on Github, but I thought I'd post it here first in case anybody else is scratching their heads at their filters. Happy to file on Github if you'd like me to.