DV-07
Fix Version or Release Target Not Set
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
An issue of a configured type in an active status has no fix version or release target assigned — it cannot be included in release planning or PI scope reporting.
Detection formula
release_field = config.discipline.release_target_field // e.g. \'Fix Version\', \'Target PI\', \'Release\' IF issue.type IN config.discipline.release_field_required_types AND issue.status IN config.workflow.active_statuses AND field_value(release_field) IS EMPTY THEN FLAGExamples 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 an issue of a configured type in an active status has no fix version or release target assigned while release target field is set to fixVersion.
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
An issue of a configured type in an active status has no fix version or release target assigned — it cannot be included in release planning or PI scope reporting.
Why it matters
When "Fix Version or Release Target Not Set" 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 "Fix Version or Release Target Not Set" 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.