Defect Trend Reports

Defect trend reports track how defects change over time using different breakdown dimensions. Use these reports to monitor defect patterns, assess quality trends, identify resolution bottlenecks, and make informed decisions about release readiness.

Understanding Defect Trends

Defect trend reports visualize the number of defects over time using stacked area charts, helping teams:

• Track defect growth and reduction patterns
• Identify priority shifts (critical defects increasing)
• Monitor resolution effectiveness
• Assess workflow bottlenecks (defects stuck in certain statuses)
• Make data-driven release go/no-go decisions
• Validate quality improvement initiatives

Unlike snapshot reports, trend reports show patterns over days, weeks, or months, revealing whether quality is improving, degrading, or stable.

Available Defect Trend Reports

Defect Priority Trend Report

Tracks defects by their assigned priority value over time within the selected project.

Best for:

• Monitoring critical and high-priority defect trends
• Identifying priority inflation (everything becomes "critical")
• Release planning based on priority distribution
• Focusing team attention on highest priority issues

What it shows:

• Stacked area chart with defects broken out by priority (Critical, High, Medium, Low, etc.)
• Each color band represents a priority level
• Chart height shows total defect count
• Trends over time showing priority distribution changes

Key insight: Use this to track the growth in the number of defects at different priority levels as teams move through the backlog. If critical defects are increasing, it signals quality degradation requiring immediate attention.

Use this when:

• Planning releases (assess critical defect count before go-live)
• Prioritizing team focus (too many high-priority defects?)
• Validating triage process (is priority assigned appropriately?)
• Tracking quality trends by severity

Defect Resolution Trend Report

Tracks the total number of defects over time by resolution status.

Best for:

• Understanding how defects are being resolved
• Identifying resolution patterns and effectiveness
• Tracking different resolution types (Fixed, Won't Fix, Duplicate, etc.)
• Analyzing team's approach to defect resolution

What it shows:

• Stacked area chart with defects broken out by resolution status
• Each color band represents a resolution type (Fixed, Won't Fix, Cannot Reproduce, Duplicate, etc.)
• Chart height shows total defect count
• Trends showing how resolution patterns change over time

Key insight: This report helps you understand resolution effectiveness. A high number of "Cannot Reproduce" defects may indicate insufficient defect reporting. Many "Won't Fix" defects might signal scope management issues or technical debt accumulation.

Use this when:

• Assessing resolution quality (are defects actually being fixed?)
• Identifying process issues (too many duplicates or cannot reproduce?)
• Planning technical debt management (tracking won't fix and deferred defects)
• Retrospectives discussing defect handling effectiveness

Defect Status Trend Report

Tracks defects by workflow status value over time (e.g., Ready for Dev, Developing, Ready for Test, Testing).

Best for:

• Identifying workflow bottlenecks
• Monitoring defect progression through development lifecycle
• Assessing team velocity on defect resolution
• Release readiness evaluation

What it shows:

• Stacked area chart with defects broken out by status (Ready for Dev, Developing, Ready for Test, Testing, etc.)
• Each color band represents a workflow status
• Chart height shows total defect count
• Trends showing movement through workflow stages

Key insight: Use this to track defect growth and progression through resolution. If defects are accumulating in "Ready for Test," it indicates a testing bottleneck. Many defects in "Ready for Dev" suggest development capacity issues.

Use this when:

• Identifying process bottlenecks (where are defects getting stuck?)
• Balancing team capacity (too many defects waiting?)
• Planning releases (how many defects are close to done?)
• Improving workflow efficiency

Choosing the Right Defect Trend Report

Report	Breakdown By	Best For	Primary Users	Key Question Answered
Priority Trend	Priority level	Release readiness, severity tracking	Product Owners, Release Managers	Are critical defects increasing?
Resolution Trend	Resolution type	Resolution effectiveness, process quality	QA Leads, Process Improvement	How are we resolving defects?
Status Trend	Workflow status	Bottleneck identification, flow efficiency	Scrum Masters, Team Leads	Where are defects getting stuck?

Accessing Defect Trend Reports

From All Reports:

1. Click the hamburger menu → Reports → All Reports
2. Scroll to the Testing and Quality Reports section (or Project or Increment Reports section)
3. Click the specific defect trend report you need

Report location variations:

• Defect Priority Trend: Available in Project/Increment Reports and Testing/Quality Reports sections
• Defect Resolution Trend: Available in Project/Increment Reports and Testing/Quality Reports sections
• Defect Status Trend: Available in Testing/Quality Reports section

Common Report Filters and Parameters

All defect trend reports share these common filters:

Sprint or Iteration

Shows data assigned to specific sprint or iteration. Default value is "All".

Use to: Focus on defects in a specific sprint or view cross-sprint trends.

Team

Shows team-specific data for the project or program. Default value is "All" or "Blank".

Use to: Compare defect trends across teams or focus on a single team.

Backlog Group

Shows data assigned to the selected backlog group.

Use to: Filter defects by product area or component.

Member

Shows data applicable to the selected member.

Use to: View defects assigned to or created by specific team member (Priority and Resolution Trend only).

Start Date

The first date the report begins calculating data.

Defaults:

• Project-based reports: Project start date
• Sprint/iteration-based reports: Sprint/iteration start date
• Member-based reports: 13 weeks prior to current date

Note: If start date is set to current date or later, no data displays.

Interval (or Duration)

The number of days, weeks, or months to display.

Defaults:

• Project-based reports: Number of weeks from project start to today
• Sprint/iteration-based reports: Number of days in the sprint/iteration
• Member-based reports: 13 weeks

Note: Report ends at current date. If selected start date and interval extend past current date, no data displays after current date.

Show Closed Workitems (Priority and Status Trend)

Check this box to show closed items within the report.

Use to: View complete defect history including resolved defects, not just open ones.

Show Only Closed Defects (Resolution Trend)

Check this box to show only closed defects in the report.

Use to: Focus analysis on defects that have been resolved.

Prerequisites

All Defect Trend Reports Require:

Minimum two data points: All Digital.ai Agility trend reports require at least two data points. If not enough data is available, the report may be blank. Depending on the duration you select in the filters, at least one complete period of data must be available to draw a trend line. When selecting days, this means the minimum duration is actually 2 days, which includes 2 data points.

Weekend settings consideration: Your Show Weekend report settings may affect how much data is selected. For example, if you choose two days as duration and one day is a Saturday or Sunday, and you have elected to not Show Weekends, you may not have sufficient data to show a trend.

Customization

All defect trend reports support customization of the dimension values to meet your organization's needs.

Customizing Priority Values (Priority Trend)

Members with System Administrator privileges can customize priority values:

1. Click the administration icon → List Types → Global → Workitem Priority
2. Modify priority values as needed
3. Changes apply to all projects

Example priorities: Critical, High, Medium, Low, or custom values like P0, P1, P2, P3.

Customizing Resolution Values (Resolution Trend)

Members with System Administrator privileges can customize resolution values:

1. Click the hamburger menu → Administration → List Types → Global → Workitem Priority
2. Modify resolution values as needed

Common resolution values: Fixed, Won't Fix, Cannot Reproduce, Duplicate, Deferred, By Design.

Customizing Status Values (Status Trend)

Members with System Administrator privileges can customize status values:

1. Click the hamburger menu → Administration → List Types → Backlog → Backlog Status
2. Modify status values as needed

Note: Status values may also vary depending on workspace settings for your selected project. Teams using custom team processes can define their own status workflows.

Using Defect Trend Reports Effectively

For Release Planning

Assess Release Readiness:

1. Review Defect Priority Trend to check critical and high-priority defect counts
2. Examine Defect Status Trend to see how many defects are close to resolution
3. Check Defect Resolution Trend to ensure defects are being fixed (not just deferred)
4. Establish go/no-go criteria based on acceptable defect counts and trends

Set Quality Gates:

• No more than X critical defects
• Decreasing trend in high-priority defects over last 2 weeks
• Minimal defects in "Ready for Dev" status (workflow clear)
• Majority of closed defects resolved as "Fixed" (not deferred)

For Sprint Planning

Before Sprint Planning:

1. Review Defect Status Trend to understand current defect inventory
2. Check Defect Priority Trend to identify critical defects needing attention
3. Assess defect resolution capacity based on recent trends

During Sprint Planning:

1. Allocate capacity for defect resolution based on trends
2. Prioritize defects using Priority Trend report
3. Consider workflow capacity using Status Trend report

For Process Improvement

Identify Bottlenecks:

1. Use Defect Status Trend to find workflow stages where defects accumulate
2. Analyze why defects get stuck (capacity, dependencies, unclear requirements)
3. Implement process changes to address bottlenecks
4. Monitor Status Trend to validate improvements

Improve Resolution Effectiveness:

1. Review Defect Resolution Trend for "Cannot Reproduce" and "Duplicate" patterns
2. Address root causes (better defect reporting, improved triage)
3. Track changes in resolution distribution over time
4. Reduce non-fixed resolutions through process improvements

Assess Quality Initiatives:

1. Establish baseline using all three defect trend reports
2. Implement quality improvements (code reviews, automated testing, etc.)
3. Compare trends before and after to validate effectiveness
4. Adjust initiatives based on trend data

For Daily Management

Weekly Reviews:

1. Check Defect Priority Trend for critical defect increases
2. Monitor Defect Status Trend for workflow issues
3. Address bottlenecks proactively before they become critical

Sprint Reviews:

1. Present defect trends to stakeholders
2. Discuss quality trajectory using all three perspectives
3. Celebrate improvements in defect resolution rates
4. Address concerning trends with action plans

Common Patterns and Insights

Healthy Patterns

Priority Trend:

• Critical and high-priority defects decreasing over time
• Low and medium-priority defects stable or decreasing
• No sudden spikes in critical defects

Resolution Trend:

• Majority of defects resolved as "Fixed"
• Low percentage of "Cannot Reproduce" and "Duplicate"
• Minimal "Won't Fix" or "Deferred" (well-managed scope)

Status Trend:

• Defects flowing smoothly through workflow stages
• Minimal accumulation in any single status
• Total defect count decreasing over time

Warning Patterns

Priority Trend:

• Critical defects increasing (quality degradation)
• Priority inflation (everything becomes high priority)
• Sudden spikes indicating systemic issues

Resolution Trend:

• High percentage "Cannot Reproduce" (poor defect reporting)
• Many "Duplicates" (inadequate triage process)
• Increasing "Won't Fix" or "Deferred" (technical debt accumulation)

Status Trend:

• Defects accumulating in specific status (bottleneck)
• Total defect count growing (creation exceeds resolution)
• Defects stuck in early stages (capacity issues)

Action Patterns

Quality crisis detected (Priority Trend: critical defects spiking):

• Hold war room to address critical defects
• Assign dedicated team to critical defect resolution
• Pause new feature work if necessary
• Implement quality gate to prevent new critical defects

Workflow bottleneck detected (Status Trend: accumulation):

• Analyze capacity at bottleneck stage
• Redistribute team resources temporarily
• Remove impediments blocking defect flow
• Adjust workflow if structural issue identified

Resolution effectiveness issue (Resolution Trend: high non-fixed rate):

• Improve defect reporting guidelines
• Enhance triage process with clear criteria
• Train team on defect reproduction steps
• Implement better debugging tools and processes

Technical debt accumulation (Resolution Trend: many deferred):

• Create technical debt backlog
• Schedule regular debt paydown sprints
• Assess impact of deferred defects
• Set limits on deferral rate

Troubleshooting: Multiple Same Statuses Shown

Issue

Multiple identical statuses appear on the Defect Status Trend Report, creating duplicate entries in the legend and confusing visualization.

Example: You see "In Progress" appearing twice or "Testing" showing multiple times in the chart legend.

Why This Happens

This occurs when:

1. Report filtered on "All Teams" and
2. Custom team processes enabled with different status definitions per team

Each team's custom process may have similar or identically named statuses, but they're technically different status values in the system. When viewing "All Teams," the report shows all status variations, resulting in apparent duplicates.

Resolution

Best practice: Filter the Defect Status Trend Report by individual team when custom team processes are enabled.

To resolve:

1. Open the Defect Status Trend Report
2. In the Team filter, select a specific team instead of "All"
3. Click Go to refresh the report
4. View each team's report individually

This eliminates duplicate statuses and provides a clear, concise view of defects and their statuses within each team's custom workflow.

Alternative approaches:

• Standardize team processes: If all teams follow similar workflows, consider using a shared process instead of custom processes per team
• Use different status names: Ensure each team uses unique status names if custom processes are necessary
• Filter by project: If teams work in separate projects, filter by project instead of team

Best Practices

Review cadence:

• Daily: Check Priority Trend for critical defect changes during active release
• Weekly: Review all three trends for patterns and bottlenecks
• Sprint review: Present defect trends to stakeholders
• Monthly: Analyze long-term quality patterns and process effectiveness

Data quality:

1. Ensure consistent priority assignment using clear criteria
2. Update defect status regularly (at least daily during active work)
3. Use resolution values accurately (don't misuse "Won't Fix" as a catch-all)
4. Close defects promptly when resolved
5. Maintain accurate team and sprint assignments

Analysis tips:

• Look for patterns over 3-5 data points minimum
• Consider external factors (releases, holidays, team changes)
• Compare trends across multiple sprints for context
• Use all three reports together for complete quality picture
• Correlate defect trends with release dates and deployment events

Cross-report analysis:

• Priority + Status: Are high-priority defects moving faster through workflow?
• Priority + Resolution: Are critical defects

actually being fixed or deferred?

• Status + Resolution: Do bottlenecks correlate with resolution types?
• All three: Complete quality trajectory for release readiness assessment

Avoid:

• Making decisions based on single data points
• Ignoring context (new feature releases typically increase defects)
• Using trends to blame individuals or teams
• Focusing solely on defect count without considering severity
• Deferring too many defects (creates technical debt)

Integration with Other Reports

Complementary Quality Reports

Combine with Test Reports:

• Defect Trends + Test Trend Report: Quality from both defect and test perspectives
• Defect Trends + Test Runs Report: Internal quality vs external test results

Combine with Sprint Reports:

• Defect Status Trend + Sprint Burndown: Defect impact on sprint progress
• Defect Priority Trend + Velocity Reports: Quality vs delivery speed trade-offs

Combine with Project Reports:

• Defect Trends + Cumulative Flow: Overall project health including quality
• Defect Trends + Scope Change Report: Understanding scope changes from defect discoveries

Cross-Report Analysis

Quality-Speed Balance:

1. Compare Defect Priority Trend with Velocity Reports
2. Assess whether velocity increase correlates with quality decrease
3. Find sustainable pace balancing speed and quality

Release Readiness Assessment:

1. Review Defect Priority Trend for severity distribution
2. Check Defect Status Trend for resolution timeline
3. Examine Test Trend Report for test coverage
4. Combine data for comprehensive go/no-go decision

Technical Details

Chart Visualization

Stacked Area Chart:

• X-axis: Time (days, weeks, or months)
• Y-axis: Number of defects
• Color bands: Each dimension value (priority, resolution, status)
• Total height: Total defect count on that date

Reading the Chart:

• Wider bands indicate more defects in that category
• Band height changes show trends for specific dimension values
• Overall chart height shows total defect count changes
• Color changes over time reveal shifts in distribution

Report Performance

• Trend reports over long periods may take longer to generate
• Use filters to focus on relevant timeframes and teams
• Export large reports for offline analysis
• Consider shorter intervals for faster rendering

Data Refresh

• Reports show real-time or near-real-time data
• Historical data requires time for aggregation
• Minimum 2 complete data points needed for trends
• Weekend data may be excluded based on settings

Related Topics

• Testing and Quality Reports: Overview of all quality reports
• Issue Trend Report: Track issues (different from defects) over time
• Test Trend Report: Monitor test status changes over time
• Test Runs Report: External test system integration results
• Sprint or Iteration Reports: Sprint-specific metrics
• Project or Release Reports: Project and release-level tracking
• Team Process Management: Custom workflow configuration