Bring findings into the review
Read bugs, vulnerabilities, code smells, and quality gate status with your delivery and project context.
Code Quality & Security
Connect SonarQube findings, quality gates, coverage, and technical debt with team and delivery context. See where issues are concentrated and what needs follow-up.
SonarQube · 3 projects in view
| Project | Quality gate | Bugs | Vulnerabilities | Code smells | Coverage | Debt |
|---|---|---|---|---|---|---|
| Payments API | Failed | 9 | 2 | 87 | 68.4% | 12d |
| Platform Services | Passed | 3 | 0 | 42 | 84.2% | 8d |
| Mobile Backend | Failed | 6 | 1 | 61 | 71.6% | 16d |
Payments API and Mobile Backend have failed quality gates. Inspect their findings and remediation priorities with the teams.
Choose “Needs attention” to focus the project view on failed quality gates.
From signals to decisions
Make quality part of the same review as contribution, delivery, and remediation.
Read bugs, vulnerabilities, code smells, and quality gate status with your delivery and project context.
Connect quality issues to contributors and teams. Review ownership with the code and responsibilities behind the finding.
Review technical debt and quality movement over time. Keep the next action visible in the engineering review.
What to look at
Bring the quality signals reported by SonarQube into your engineering review, using consistent project and team scope.
What to look at
Use quality movement to focus the investigation, then review the work and follow up on the result.
Common questions
Need to discuss your team or technical setup? Contact us.
Review SonarQube bugs, vulnerabilities, code smells, quality gates, technical debt, maintainability, reliability, and test coverage. Availability depends on the connected source and its reports.
Oobeya supports SonarQube Server and SonarQube Cloud integration scenarios. Review the integration catalog for your environment and connection requirements.
Oobeya connects code quality issues with contributor and team context so quality can be discussed alongside engineering work and delivery.
Yes. Use the technical debt timeline and related quality signals to review where remediation effort is accumulating and whether follow-up work changes the trend.
A gate reflects the conditions configured in the quality system. Review the underlying findings, coverage, scope, and related delivery signals when assessing quality.
Read quality findings with Team Performance, Delivery Symptoms, and production DORA trends to investigate the work and workflow around an outcome.
See Oobeya in practice
Walk through SonarQube findings, quality gates, technical debt, and engineering context with your team’s priorities in mind.