Burndown not showing total REMAINING TIME ESTIMATE

[Sourabh Agrawal]

I have total 500 + remaining time estimate in sprint however when I started the sprint, the burndown only showing 64 odd REMAINING TIME ESTIMATE

[Petter Gonçalves]

Hello @Sourabh Agrawal

Thank you for reaching out.

Per your description, I understand that the remaining estimate displayed in your burndown chart is not the same that was displaying in your backlog when starting a new Sprint. Is that correct?

Also, can you confirm if you are using Jira Next-gen or Classic projects?

This mismatch can be caused by several reasons. The most common are the following ones:

1. Your board filter could be hiding some issues of the Sprint to be displayed on the board. I would check in your burndown chart what are the issues that are displayed with a high number of remaining estimate and check if they would be displayed in the Sprint view
2. A change in the board filter after the start of the Sprint could also cause the same behavior mentioned in step 1
3. If you manually change the estimation of issues during the Sprint progress, the total remaining estimate will also be changed in the burndown chart.
4. You can be using the wrong field to estimate your issues. (Jira Next-gen and Classic projects uses different fields for time tracking)

If I misunderstood your scenario or you confirmed that the reasons above did not cause the mismatch, please provide us with some screenshots or video so we can get more details about the problem.

Let us know if you have any questions.

[Sourabh Agrawal]

Thank you for reaching out.

Per your description, I understand that the remaining estimate displayed in your burndown chart is not the same that was displaying in your backlog when starting a new Sprint. Is that correct?

SA: that correct

Also, can you confirm if you are using Jira Next-gen or Classic projects?

SA: next-gen projects

This mismatch can be caused by several reasons. The most common are the following ones:

1. Your board filter could be hiding some issues of the Sprint to be displayed on the board. I would check in your burndown chart what are the issues that are displayed with a high number of remaining estimate and check if they would be displayed in the Sprint view

SA: The filter is correct and what I have observed is the subtask effort is not getting calculated in the story that's why the burndown is not showing the correct picture. Ex. https://itmebusiness.atlassian.net/browse/IPP-3513

1. A change in the board filter after the start of the Sprint could also cause the same behavior mentioned in step 1
2. If you manually change the estimation of issues during the Sprint progress, the total remaining estimate will also be changed in the burndown chart.
3. You can be using the wrong field to estimate your issues. (Jira Next-gen and Classic projects uses different fields for time tracking)

If I misunderstood your scenario or you confirmed that the reasons above did not cause the mismatch, please provide us with some screenshots or video so we can get more details about the problem.

Let us know if you have any questions.