Sort code quality violations in full code quality report by severity
Based on an actionable insight from the UX Department: MRs experience async critique research (insight) we want to better organize the full code quality report.
What
In the full code quality report, there is a lot of item duplication. There is no information hierarchy or typography differences.
Why
With so much duplicated content, it's difficult to focus on what makes each issue different. It also makes it hard to ignore a specific group of similar/identical issues.
How
- Code Quality violations should be sorted by severity descending (Highest to lowest - Blocker, critical, major, minor, info)
Edited by Ricky Wiens