From my understanding, the only possible issue dependent Quality Gate rule is the general “Issues” rule which sets a failing Quality Gate if the total number of issues is greater than the set value.
I think it would be a good idea to allow defining finer rules to limit the number of issues for each type. For example, I would like to be able to configure values x, y and z, where each one of them configures the maximum number of security, bug and maintainability issues (respectively). The way I imagine it, there will be 3 new configurable rules in addition to the existing “Issues” rule which will remain as-is.
This will allow for much more control over the Quality Gate for those who need it.
In our code base specifically it will be very useful as we encounter a significant amount of false positive maintainability issues which we want to allow without blocking integration, but the bug and security issues are almost always on point and we want to block integration if any of those appear.