DV-11
Issue Added to Sprint Without Story Points
Discipline
Default severity: medium
ProcessMetricsQuality
What it detects
An issue was added to a sprint with no story points — it was planned without an estimate. Sprint commitment is unreliable and velocity will be inaccurate. sprint_add_date = changelog.find(field=\'sprint\', new=sprint.id).date sp_at_addition = field_value(\'story_points\', AT sprint_add_date)
Detection formula
IF issue.type IN config.estimation.required_estimate_types AND (sp_at_addition IS NULL OR sp_at_addition = 0) THEN FLAG IF issue.status = Done AND sp still NULL THEN CRITICAL (velocity invisible)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 an issue was added to a sprint with no story points while required estimate types is set to Configured per workspace.
Suggested response
Enforce assignee, field, hierarchy, and sprint hygiene rules your team agreed on.
Coaching playbook
Symptom
An issue was added to a sprint with no story points — it was planned without an estimate. Sprint commitment is unreliable and velocity will be inaccurate. sprint_add_date = changelog.find(field=\'sprint\', new=sprint.id).date sp_at_addition = field_value(\'story_points\', AT sprint_add_date)
Why it matters
When "Issue Added to Sprint Without Story Points" 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 "Issue Added to Sprint Without Story Points" 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.