You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
This post appears to be a continuation of an earlier thread:
I encourage responders to put their responses on the original thread.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.