Follow the backlog trend
Review whether open defects are accumulating or being resolved over time. Keep the period and project scope consistent.
Bug & Defect Analytics
See the bugs, severity, and ownership behind the backlog
Follow open defects over time and inspect where risk is concentrated. Move from the trend into project, severity, assignee, and issue-level detail.
Bug & Defect Analytics
Open backlog and severityDefect backlog overview
All projects · Open issues
- Open defects
- 8
- Critical
- 2
- High severity
- 3
- Oldest open issue
- 14 days
Open defect trend · All severities
Open defectsExplore the trend
Open issues 8
| Issue | Project | Severity | Assignee | Age |
|---|---|---|---|---|
| PAY-142Payment callback retry fails | Payments | Critical | Maya Patel | 14d |
| MOB-87Session refresh loses state | Mobile | High | Alex Morgan | 9d |
| PLAT-54Build status mapping mismatch | Platform | Medium | Sam Taylor | 6d |
| PAY-148Invoice total rounding mismatch | Payments | High | Jordan Lee | 5d |
| WEB-91Filter label does not refresh | Web | Low | Alex Morgan | 4d |
| MOB-93Login request fails after upgrade | Mobile | Critical | Sam Taylor | 3d |
| PLAT-62Webhook delivery not retried | Platform | High | Maya Patel | 2d |
| WEB-99Export omits selected column | Web | Medium | Jordan Lee | 1d |
Filter the issue list by severity to inspect the work items and owners behind the backlog.
From signals to decisions
Read volume, severity, and ownership together
Use the backlog trend to focus the review, then inspect the issues that need attention.
Inspect the severity mix
Separate critical, high, medium, and low findings. Investigate the issues driving a change in delivery or quality risk.
Find where ownership sits
Review team, project, and assignee details so the follow-up can be discussed with the people responsible for the work.
What to look at
Keep defect reporting connected to the work items
Use your connected issue tracking data to inspect the backlog and the detail behind it.
- Jira and Azure Boards
- Work item type and project scope
- Severity and status mapping
- Team, assignee, and issue detail
- Jira bug data
- Bring issue type, severity, assignee, project, and status into the defect review from the connected Jira scope.
- Azure Boards work items
- Use board-driven work item data to follow open defects, team ownership, and backlog movement.
- Consistent mapping
- Review the work item types, severity mappings, and team associations used in your environment before comparing projects.
What to look at
Follow a backlog signal into the next action
Keep the trend, affected issues, and follow-up in the same engineering review.
- Open-defect trend
- Critical and high-severity concentration
- Assignee and project context
- Test and delivery follow-up
- Identify the change
- Start with the open-defect trend and the severity mix. Locate the projects and teams where backlog pressure is changing.
- Inspect the affected work items
- Review the issue, assignee, severity, and status. Discuss the priority and any workflow constraints with the responsible team.
- Follow the backlog after action
- Review the same scope again after prioritization or remediation work. Compare the trend with test and delivery outcomes.
Common questions
Bug and defect analytics questions
Need to discuss your team or technical setup? Contact us.
What does Bug & Defect Analytics show?
Review open-defect trends, severity distribution, team and project context, assignees, and issue-level detail.
Which systems can provide defect data?
Jira and Azure Boards provide work item data for this view. Review the configured issue types, severity, status, and team mapping for your environment.
Can we inspect critical and high-severity bugs?
Yes. Use the severity view to focus the issue list and inspect the relevant work items, owners, and project context.
Can leaders compare bug load across teams?
Yes. Review team distribution with the mapped work items and project scope to understand where the backlog is concentrated.
Does a falling bug count mean quality improved?
Inspect severity, status changes, scope, incoming defects, and test or delivery outcomes alongside the count. A total alone does not explain the change.
How does this relate to Test Analytics?
Test Analytics brings execution and escaped-defect context. Bug & Defect Analytics helps inspect the open work items, severity, ownership, and backlog trend.
See Oobeya in practice
Bring the defect backlog into your next review
Walk through open defects, severity, ownership, and source mappings with your engineering and quality teams.