- ALM used Azure DevOps
- CI system used Azure DevOps
- Languages of the repository - C#, Objective-C and Java
- Error observed- Previously on the main Dashboard we used to see the overall cards. One of the important cards which shows total # of Maintainability pending issues. On this same card the number of issues are separated based on the issue severity (High, Medium and Low). It was so intuitive and easily readable. But now, we can’t see the severity-wise # of issues. We need this back.
- Steps to reproduce - On the homepage, 1) Open the project 2) Main Branch tab 3) Overall Code 4) The 3rd card shows the total # of Maintainability pending issues, but not the severity-wise # of issues.
- Potential workaround- Start showing the severity-wise # of pending issues
Hey @TejasPawar
Thanks for your feedback. Just so you know, this was an intentional change made back in October seeing as we restored 5-levels of severity for issues on SonarCloud.
It’s the first time we receive feedback on this, so I’m pinging the relevant decision maker here.
Thanks Colin. I understand that this change was done to improve the severity levels of the issues. Is there any way we can customise this and make the counts visible on the main dashboard.
Furthermore, I couldn’t decipher this line of yours - “I’m pinging the relevant decision maker here.” Could you help me understand what does it mean.
Hi @TejasPawar ,
Colin means that he was making sure I had seen your feedback because this is an area I am responsible for. With the move to 5 severities we thought that breaking the counts down into 5 chunks instead of 3 would make the UI too busy. I’ll take your feedback to our team so that we can consider it as we move forward.
Is it just the maintainability issues where the breakdown by severity is useful for you?
Thank you for your feedback!
John
Thanks John.
We would like to have the breakdown by severity on all the cards (Security, Reliability & Maintainability). This helps us convey the progress efficiently to our higher management.
Thank you for the additional information @TejasPawar.