Resolving Jira Sprint Burndown Chart Issues: Investigating Solutions for Accurate Data Display

[Shuo Ping]

In Jira's Sprint burndown chart report, there are often bugs with the issue count, resulting in negative numbers or discrepancies between the chart and actual data. For example, issues that have already been resolved do not cause the curve to decrease in the chart. We would like to investigate a solution to ensure that the numbers displayed in the chart are correct. We have looked at some solutions in the community, but they have not worked (including selecting "Adjust Automatically" for each issue when logging work). Could you please advise on any possible solutions? Thank you.

[Brant Schroeder]

@Shuo Ping Welcome to the Atlassian community.  Can you share some screenshots of what you are seeing?   

[Shuo Ping]

Thank you for your response! As shown in Figure 1, the curve in the report chart we obtained contains negative numbers. The second image shows the number of issues we currently have, so we are unsure why there are negative values in the chart. In recent days, I have noticed that when we change the status of an issue to "closed" or "resolved", it is not being counted as completed in the report calculation, which may be causing negative outcomes in the chart.

[Brant Schroeder]

@Shuo Ping There are no issues attached.

[Shuo Ping]

Please check the above files.

[Brant Schroeder]

@Shuo Ping Looks fine.  I think that this could be your issue - https://confluence.atlassian.com/jirakb/negative-remaining-value-on-burndown-chart-779158672.html 

[Shuo Ping]

Thank you for helping!  We have tried the "auto-adjust remaining estimate" option, but negative numbers still appear in the report. After investigating, we found that there is duplicate calculation of the issue resolution status in the log, and we would like to ask if this can also cause negative numbers to appear in the report chart. If so, how can we solve the problem of duplicate calculation? Thank you.