CH-09
Issue Reassigned Between Parent Issues
Content & History
Default severity: medium
Product BacklogProcessQuality
What it detects
An issue was reassigned from one parent (epic/feature) to another after entering an active status, more than the configured maximum number of times.
Detection formula
parent_field = config.workflow.parent_link_field // e.g. \'Epic Link\', \'Parent\' parent_changes_post_activation = changelog.filter(field=parent_field, date > first_active_date) IF COUNT(parent_changes_post_activation) >= config.content.max_parent_changes // default: 1 THEN FLAG IF COUNT >= config.content.critical_parent_changes // default: 2 THEN CRITICAL (nomad issue)Examples in practice
- Set at creation; never changes
- A team shows an issue was reassigned from one parent (epic/feature) to another after entering an active status, more than the configured maximum number of times while parent link field is set to Configured per workspace.
- Example signal: An issue was reassigned from one parent (epic/feature) to another after entering an active status, more than the configured maximum number of times.
Suggested response
Protect narrative quality: write items before work starts and avoid late or empty edits.
Coaching playbook
Symptom
An issue was reassigned from one parent (epic/feature) to another after entering an active status, more than the configured maximum number of times.
Why it matters
When "Issue Reassigned Between Parent Issues" 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
Protect narrative quality: write items before work starts and avoid late or empty edits.
Facilitation questions
- What system change would stop "Issue Reassigned Between Parent Issues" 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.