Bugs Resolved Per Member

Count of bugs resolved per active member in the team. The definition of Bug is mapped to your underlying Issue tracking tool (Jira, Linear, ClickUp etc). For teams, this is an average metric, for individuals the Bugs resolved & Bugs Resolved Per Member have the same value.

• Jira - issue type = Bug
• Clickup - issue type = Bug
• Azure boards - issue type = Bug
• Linear - every issue is considered as Task. There is no bug distinction as of now.

Computation of the metric

1. Computed by counting the issues labeled as bugs that have transitioned to a "Resolved" or "Closed" status within a specified timeframe.
2. The "Bugs resolved per member" metric is then calculated as the ratio of the total number of bugs to the number of members in the selected team.
3. Data is sourced from project management tools such as Jira, where bug statuses are tracked.

Dashboards where this metric is used

1. Dev Metric Grid
2. Effort Alignment

Use cases of this metric

1. Provides a way to compare teams on bugs/product quality by averaging out the bugs per member.
2. By tracking the total count of bugs resolved, teams can monitor their performance in addressing and resolving issues, enabling them to identify trends, patterns, and areas for improvement in the bug resolution process.
3. Benchmarking the total count of bugs resolved over time enables teams to set goals for continuous improvement and track progress. It facilitates the implementation of strategies to enhance bug resolution processes, leading to more robust and reliable software products.