DV-25
Inconsistent Hierarchy — Story Without Parent Feature
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
A Story exists without being linked to a parent Feature or Epic — it is an orphan in the hierarchy. Orphan stories cannot be traced to a business objective and are invisible to portfolio-level reporting.
Detection formula
parent_fields = config.workflow.parent_link_fields // \[\'Epic Link\', \'Parent\', \'Feature Link\'\] IF issue.type IN config.workflow.story_types AND ALL(field_value(f) IS NULL FOR f IN parent_fields) AND issue.status NOT IN config.workflow.initial_statuses THEN FLAG orphan_storyExamples 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 story exists without being linked to a parent feature or epic while parent link fields is set to Configured per workspace.
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
A Story exists without being linked to a parent Feature or Epic — it is an orphan in the hierarchy. Orphan stories cannot be traced to a business objective and are invisible to portfolio-level reporting.
Why it matters
When "Inconsistent Hierarchy — Story Without Parent Feature" 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 "Inconsistent Hierarchy — Story Without Parent Feature" 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.