DV-26

Feature Without Parent Epic

Discipline

Default severity: medium
ProcessMetricsQuality

What it detects

A Feature exists without being linked to a parent Epic or Initiative — it has no traceable strategic objective. Orphan features cannot be included in PI scope or portfolio reporting.

Detection formula

IF issue.type = config.workflow.feature_type AND ALL(field_value(f) IS NULL FOR f IN config.workflow.parent_link_fields) AND issue.status NOT IN config.workflow.initial_statuses THEN FLAG orphan_feature

Examples in practice

  • Assignee, field, hierarchy, or sprint hygiene rules are violated on active work.
  • Issues miss mandatory fields or ownership while still in progress.
  • A team shows a feature exists without being linked to a parent epic or initiative while feature type is set to Configured per workspace.

Suggested response

Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.

Coaching playbook

Symptom

A Feature exists without being linked to a parent Epic or Initiative — it has no traceable strategic objective. Orphan features cannot be included in PI scope or portfolio reporting.

Why it matters

When "Feature Without Parent Epic" 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

Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.

Facilitation questions

  • What system change would stop "Feature Without Parent Epic" 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 tourSign in
DV-26: Feature Without Parent Epic — FlowAnalyzer