nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Burndown chart not showing any data

Susie Barber_61tm1w

Last night we finished a sprint and started a new sprint. The previous sprint shows the burndown chart as expected (and has been since we started using burndown charts). The burndown chart for the new sprint (started) shows nothing, despite having 94 tickets, most with story points. What's happened and how do I fix this?

Here is the burndown chart for the previous and current sprints:

Screenshot 2024-02-21 at 11.05.58 AM.png

Accepted answers

Susie Barber_61tm1w

Thanks everyone for your ideas. The burndown data is there today. Yesterday was the first day of a new sprint and as soon as the day ended, everything looked good. I think it all boils down to not showing burndown on the first day of the sprint.

All comments

Matt Parks

What's the current story point total in your active sprint? Have you completed any work items in the current sprint? And, by "completed" I mean have you moved any of the work items into a status that is represented in the far-right column of your board? I'm assuming that you don't actually reduce the total of Story Points as you move through the workflow, but the burndown chart gets updated as work is completed.

If you haven't yet completed anything, maybe the Y-axis doesn't go as high as the number of Story Points you have in your sprint? I'd be curious to see if the chart gets updated appropriately as you begin to complete work items.

Susie Barber_61tm1w

Story point total is 129 and we have completed a few tickets. The y-axis should hold the number of story points we have.

Danut M _StonikByte_

Hi @Susie Barber,

Perhaps the sprint Start Date was a bit ahead, and those issues appears as being done before sprint Start Date. Look also at the table under the burndown chart from the report, to see what happens with those issues and the dates.

Also, as an alternative to this report, you could try the Sprint Burndown Burnup Chart gadget offered by our Great Gadgets app.

On its Data tab, you have a table with the Sprint Report - so you can compare these with the Jira report to see were the differences come from.

If it displays correct data, then this might be a bug in the Jira's report.

Hope this helps.

Danut.

Susie Barber_61tm1w

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud