My team uses your web api endpoint/measures/component to collect the Reliability Issues Count for each Sonar project in our organization. Initially I believed that Reliability Issues were identified as bugs as per the SonarQube Cloud documentation (screenshot below).
Eventually I ran across a project where the count seemed “off.” After digging further into the project’s Issues, it appeared that Reliability Issues included bugs and code smells (see second screenshot).
My question is, are Reliability Issues comprised of both Bugs AND Code Smells? If so, the Reliability and Maintainability sections appear somewhat misleading on the Understanding Measures and Metrics page (see the last two screenshots). Can you provide a little more clarity? Thank you.
Please make sure that you are referring to the SonarQube Cloud documentation, not the SonarQube Server documentation. There are key differences between the two. For example, SonarQube Server offers both multi-quality rule mode (where a bug or code smell can affect reliability) and Standard experience (where only a bug affects reliability), whereas SonarQube Cloud only supports the former.
The relevant metric key you need is reliability_issues.
Documentation for this is lacking. I’ll be flagging this with the team for improvement.
Hi Colin. Thank you for the response as well as flagging the current documentation for updates. I’m fully aware that I was looking under the SonarQube Server documentation. I could not find a similar page under the SonarQube Cloud section. If there is an equivalent page, could you please point me to it?
Also, unless I am missing something, I have never seen the reliability_issues metric key in a response from the /measures/component endpoint before. I even checked the v2 api docs. Could you also help me locate the API that returns that metric key?
