We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Agile Dashboard Burndown, Burnup, Cumulative Flow Design Graph not showing any data

UdayKiran17
Tera Contributor

Wednesday

Agile dashboards charts not showing any data in sprint dashboard, epic dashboard, i have all the configuration date for planned start date, end date, scheduled job active even though these charts showing empty, I'm able to see data in indicators.

Preview file
6648 KB
0 Helpfuls
  • 100 Views
1 REPLY 1

Vikram Reddy
Tera Guru

yesterday

Hey @UdayKiran17,

 

The fix is almost always in the Performance Analytics snapshot history, not the sprint configuration. Sprint Burndown, Sprint Burnup and Sprint Cumulative Flow Diagram are trend charts built from pa_snapshots data collected over time, while the scorecards next to them (Scope, Percent Completed, Missing Estimates, Blocked Work) are Live-style indicators that just report the current numbers. That is why you can have populated indicators and a completely empty chart underneath, they are two different mechanisms and one needs history to build a line, the other does not.

Your screenshot actually gives this away: the Scope and Percent Completed tiles both say "Data from July 15." That means snapshot collection only recently started accumulating history for this sprint. Burndown, burnup and CFD need a continuous daily series across the sprint's window (planned start through planned end) to plot the Remaining, Scope, Completed and Ideal Burndown series. If that history is short or has gaps, the widget doesn't render a partial chart, it just shows "No data to display."

Worth checking, roughly in order:

  • Job run history, not just the Active flag: open the [Scrum] Daily Data Collection scheduled job and look at its actual execution history/logs, not just whether Active is checked. A job that's enabled but has been erroring or skipping runs won't ever build the snapshot series these three charts depend on.
  • Planned Start Date vs. first snapshot date: if Sprint 6's Planned Start Date is earlier than July 15, the early part of the window simply has no snapshot rows, and the chart can't draw a series across a range it doesn't have data for. Waiting a few more collection cycles from today forward may partially fix this, but the early days will stay blank unless you're willing to accept a shorter window.
  • Planned dates edited after the job already ran that day: if you touched Planned Start Date or Planned End Date after the daily job had already fired, that day's collection won't reflect the change. Re-save the dates and manually trigger the job once (or wait for the next scheduled run) rather than assuming it'll self-correct.
  • Sprint state: confirm Sprint 6 is genuinely the active/current sprint on the Scrum Team record the dashboard is filtered to. A dashboard pointed at a sprint that isn't actually current can leave the breakdown-based widgets with nothing to plot even when the scorecards still resolve.

One thing you can rule out already: Missing Estimates is showing 0 and Blocked Work is showing 0, so this isn't a backlog data-quality problem (missing story points or blocked items skewing the breakdown). This is specifically a data-collection/history gap, so I'd start with the job's execution log rather than re-checking the sprint form again.

References

 

Thank you,
Vikram Karety
Octigo Solutions INC

0 Helpfuls