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.

[Yogesh Mude]

HI @DI IELSI Carol

Welcome to the community!

Yes, you can do this using Bulk change option.

First, you need to run the Jql like project = XXX and status =XXX or as you want then you can see the Bulk option at the right top corner on the screen.

Click on it and then you need to choose the move issue operation.

To move the issue from one project to another you should have the move issue permission for the project.

Here is the details documentation about this.

https://confluence.atlassian.com/adminjiraserver071/managing-global-permissions-802592439.html