I am trying to use the warnings-ng plugin along with the quality gates to configure which warnings will cause an unstable build.  However it seems as if the current setup for quality gates isn't granular enough to achieve what I'm looking for which is basically that either of the following conditions result in an unstable build:

• any checkstyle warnings (regardless of priority) 
• any Open tasks scanner warnings with a priority of High

However it seems like if I change the quality gates setting type to "Total number of warnings (severity high)" then my lower priority checkstyle warnings result in a passing build and if I change the type to "Total number of issues (any severity)" then my open tasks cause an unstable build, neither of which is a desirable result.

It almost seems like there would need to be another field in the quality gate to allow selection of which static analysis tool the gate should apply to (maybe with the default being "all results"?)

Note that previously we were able to do this as separate post-build actions using the deprecated "Post checkstyle analysis results" and "Scan workspace for open tasks" plugins but we'd like to avoid having to use these going forward if it's still possible to achieve this result with Warnings NG