Our release planning dashboard velocity chart hasn’t updated in 3 sprints despite completed stories. We’re using Jira Advanced Roadmaps with story points configured in the custom field “Story Point Estimate”. Sprint dates align correctly in board settings, but the velocity gadget shows flat lines.
Checked the gadget configuration:
Field: Story Point Estimate (customfield_10016)
Sprints: Last 6 completed
Chart Type: Bar
The sprint report itself shows correct burndown, but velocity chart remains at zero. Team needs this for release forecasting. Cache refresh didn’t help. Anyone encountered similar velocity chart configuration issues with story points field mapping?
Had identical issue last month. Problem was sprint date alignment - our sprints technically closed but the completion timestamp was in the future due to timezone misconfiguration. Check Admin → System → General Configuration and verify server timezone matches your team’s working timezone. Also look at individual sprint dates in Backlog view to confirm they’re not showing future timestamps despite being marked closed.
Timezone was UTC but team works in EST - that could explain the delay! Going to check sprint completion timestamps now. If that’s the root cause, do I need to manually adjust closed sprint dates or will future sprints auto-correct once timezone is fixed?
Checked estimation settings - field matches customfield_10016. All 3 sprints show “Closed” status with proper end dates. Still seeing zeros in velocity chart. The gadget seems disconnected from actual sprint data even though sprint reports work fine.
I’ve seen this when the velocity gadget cache gets corrupted after field migrations. Try removing the gadget completely from dashboard, wait 5 minutes, then re-add it. Also verify your board filter JQL includes the completed issues - sometimes filter changes break velocity tracking without obvious errors.
The flat velocity chart with working sprint reports indicates a gadget data sync issue, typically caused by story points field mapping conflicts or sprint date misalignment. Here’s the systematic fix addressing all four configuration areas:
1. Velocity Chart Configuration
Remove and recreate the gadget with explicit field selection. The gadget caches field mappings at creation time, so field changes after initial setup don’t propagate automatically.
2. Story Points Field Mapping
Verify estimation field consistency across three locations:
Board Settings → Estimation → Story Point Estimate
Project Settings → Fields → Story Point Estimate (customfield_10016)
Gadget Config → Estimation Statistic → Story Point Estimate
All three must reference the exact same custom field. Mismatches cause silent calculation failures.
3. Sprint Date Alignment
Your timezone mismatch (UTC server, EST team) causes sprints to appear “in progress” to the velocity calculator even when marked closed. Fix server timezone in System → General Configuration, then manually adjust the 3 affected sprint end dates:
Open each sprint in Backlog view
Click Edit Sprint
Set end date/time to actual completion moment in EST
Save and wait 10 minutes for gadget recalculation
4. Gadget Cache Refresh
After timezone and field corrections, force cache rebuild:
Navigate to Dashboard → Manage Dashboard
Delete velocity gadget entirely
Wait 5 minutes (critical for cache clear)
Re-add gadget with verified field configuration
Select “Last 6 completed sprints” explicitly
The gadget should populate within 15 minutes showing historical velocity for all corrected sprints. Future sprints will calculate automatically once timezone alignment is fixed. If issues persist after these steps, check Jira logs for VelocityCalculationService errors indicating deeper data integrity problems with story point values themselves.