See what's new on Keypup!  📢

Raised Bugs Tracker

Template providing the number of bugs raised in a given period.

Get started with this Dashboard

Track the Evolution of Bug Raised Overtime

with

Raised Bugs Tracker

Monitor the evolution of bugs raised month over month and identify potential bottlenecks or changes in your team’s habits.

Use the Raised Bugs Tracker Metric
Raised Bugs TrackerRaised Bugs TrackerRaised Bugs Tracker

Understand the Raised Bugs Tracker Metric

The raised bug tracker metric measures the evolutions of production defects raised by your team. The insight includes both open and closed bugs.

How to Use the Raised Bugs Tracker Metric

Using the raised bugs tracker metric may yield substantial insights for sprint retrospectives and identify bottlenecks in the development process.

Here are some examples:

  • There have been fewer reported bugs lately: This may be due to lower productivity, which implies fewer releases and fewer opportunities for bugs, or a strengthened testing process, which ensures that most bugs have been fixed before being released.‍
  • A spike in reported bugs recently: Your teams may be overburdened with development and unable to follow a proper bug fix or review flow.

How to Improve the Raised Bugs Tracker Metric

To lower the number of bugs, you can add automated code review tools and automated end-to-end (E2E) testing, increase the team’s seniority or allow senior developers to spend more time on reviews, and involve QA and product teams during the development phases to avoid back-and-forth development.

Use the Raised Bugs Tracker Metric

Understand the Raised Bugs Tracker Metric

The raised bug tracker metric measures the evolutions of production defects raised by your team. The insight includes both open and closed bugs.

How to Use the Raised Bugs Tracker Metric

Using the raised bugs tracker metric may yield substantial insights for sprint retrospectives and identify bottlenecks in the development process.

Here are some examples:

  • There have been fewer reported bugs lately: This may be due to lower productivity, which implies fewer releases and fewer opportunities for bugs, or a strengthened testing process, which ensures that most bugs have been fixed before being released.‍
  • A spike in reported bugs recently: Your teams may be overburdened with development and unable to follow a proper bug fix or review flow.

How to Improve the Raised Bugs Tracker Metric

To lower the number of bugs, you can add automated code review tools and automated end-to-end (E2E) testing, increase the team’s seniority or allow senior developers to spend more time on reviews, and involve QA and product teams during the development phases to avoid back-and-forth development.

Use the Raised Bugs Tracker Metric