Some of our quality gate shown an empty conditions on UI, however when I looking into network logs the conditions is still ther. So the quality gates still able to failing the conditions.
So almost certainly, the issue is the result of using security_hotspots and new_security_hotspots in your Quality Gate.
These metrics are forbidden from being used in Quality Gates and not selectable in the UI. You should use the Security Hotspots Reviewed metric in your Quality Gates.
As far as I can tell, this has been the case since 2020 – is it possible these are very old Quality Gates that haven’t been updated since then?
In any case, this isn’t the expected user experience and I’ll flag this for the team. You may also be able to remove these conditions by using the POST api/qualitygates/remove_condition Web API, but since I’m prevented from adding them to my Quality Gate in first place, I can’t test this.
I’m also not sure since when this is happened but last year still doable for us to update. Just realized recently we can’t do the change to the quality gate anymore. Agreed it seems due to security_hotspots since this quality gate is quite old like you said.
Thanks, will try to update it via API to remove unexpected conditions
Thanks for reporting this.
Indeed forbidden metrics are causing the issue. Our team is currently working on some changes to Quality Gates and I can confirm those changes have broken this use-case.
We are already working on a fix of UI, I’ll update this thread when it is released.