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?

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.

[Shankar Asam {Appfire}]

I am guessing the local user/group cache might be out of sync. You may try to recreate the user directory inside JIRA and verify. The best option is to disable the existing AD user directory and create a new one and sync it. I advise to do this in UAT/Stage before doing it on Production as it may lead to downtime.

[Kelsey Collins]

Was a fix ever found for this?

[J C]

Hi Paul,

We are running into the same problem, did you find a fix for this?