I have one of the issue regards to standard reports - below you can see a burndown report which looks completely the same also in sprint report. As you can see I have picked an Active sprint. Here i see something like 644 hrs as starting scope /original estimate amount.
Below you can see an overview of estimation on sub-task level which is significantly higher 502 days/4016 hrs (sub-task level) than 132 hrs (burndown) specific to original estimate or 219 days/1758 hrs (on sub-task level vs. 644hrs (burndown)
Please help me on this issue.
I see that you have found a discrepancy between the estimation hours in the burndown chart versus the estimations and time remaining found in the sprint report.
However, if I am understanding your concern correctly, this is actually expected. The main reason for this difference is also explained in View and understand the burndown chart. From that document:
When using the Burndown Chart, note that subtask behavior can vary, depending on whether or not remaining estimate and time spent is enabled for your board.
Subtask behavior when remaining estimate and time spent is enabled
Time estimates of subtasks are rolled up to the parent task.
This means that the parent task will have the total sum of all remaining estimates of the subtasks.
Perhaps you could compensate for this difference by adjusting the board settings to instead disable the remaining estimate and time spent. Steps on how to do this are in Configure estimation and tracking. After that changes is made on the board itself, try returning to the report and refresh the page. This should alter the way that report displays this.
Let me know if this helps or not.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events