What is this metric?
The amount of time it takes a bug to fix.
Why is it important?
- Help the team to establish an effective hierarchical response mechanism for bugs. Focus on the resolution of important problems in the backlog.
- Improve team's and individual's bug fixing efficiency. Identify good/to-be-improved practices that affect bug age age
Which dashboard(s) does it exist in
- Weekly Bug Retro
How is it calculated?
This metric equals to
created_date of issues in type "BUG".
This metric relies on issues collected from Jira, GitHub, or TAPD.Transformation Rules Required
This metric relies on the 'type-bug' configuration in Jira, GitHub or TAPD transformation rules to let DevLake know what CI builds/jobs can be regarded as
How to improve?
- Observe the trend of bug age and locate the key reasons.
- According to the severity level, type (business, functional classification), affected module, source of bugs, count and observe the length of bug age.