IT-06

Bug Origin Tracing — Linked Feature Quality

Issue Type Distribution

Default severity: medium

Product BacklogMetricsQuality

What it detects

Bugs are linked back to the feature or epic that introduced them (via Jira link \'caused by\' / \'relates to\' / same component + label). Features with a high bug offspring count had insufficient testing or AC at delivery — identifies which delivered features are low quality.

Detection formula

FOR each_bug B: source_feature = find_linked_feature(B, link_types=config.it.bug_origin_link_types) IF source_feature THEN bug_count(source_feature) += 1 FOR each_feature F: IF bug_count(F) >= config.it.bugs_per_feature_threshold // default: 3 THEN FLAG F as low_quality_delivery Report: features ranked by bug offspring count

Examples in practice

A team shows bugs are linked back to the feature or epic that introduced them (via jira link \'caused by\' / \'relates to\' / same component + label) while bug origin link types is set to \[\'caused by\',\'relates to\'\].
Example signal: Bugs are linked back to the feature or epic that introduced them (via Jira link \'caused by\' / \'relates to\' / same component + label).

Suggested response

Rebalance issue-type mix and debt trends so quality signals stay intentional.

Coaching playbook

Symptom

Why it matters

When "Bug Origin Tracing — Linked Feature Quality" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.

What you can achieve

Rebalance issue-type mix and debt trends so quality signals stay intentional.

Facilitation questions

What system change would stop "Bug Origin Tracing — Linked Feature Quality" from firing again?
What do the cited issues have in common — same root cause or same workaround?
Who owns the two-week experiment and how will we verify on the next import?

Run this rule against your own tracker data with Flow Analyzer.

Product tour Sign in