MI-13
Parent in Post-Development Testing With Open Children
Metric Integrity
Default severity: medium
MetricsQualityRisk
What it detects
Description is not yet published for this rule in the PRD catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- Bulk admin transitions or resolution anomalies distort cycle time and velocity metrics.
- Closure timestamps or fields suggest data repair rather than organic delivery.
- A team shows description is not yet published for this rule in the prd catalogue during analysis.
Suggested response
Audit closure and field patterns so metrics reflect real completion, not bulk admin updates.
Coaching playbook
Symptom
A parent issue is in a configured testing or post-development stage while at least one direct child remains open — still in development, not started, or not terminal. The parent signals “in test,” but active delivery work still runs in open children below.
Why it matters
Testing-stage parents with open children hide true WIP in the test column and weaken quality gates. Teams appear to be validating work that is not finished underneath — defects and rework surface late.
What you can achieve
Testing columns that mean the subtree is ready to validate — parents enter test only when children are terminal or scoped test exceptions are explicit.
Facilitation questions
- What open children are still being built while this parent is marked in testing?
- Does our workflow allow parents into test before children finish — and should it?
- What would make “in testing” a truthful signal for the whole subtree?
Run this rule against your own tracker data with Flow Analyzer.