Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Sprint Report/ Burndown Report

Vijaypal dumpala
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 3, 2020

we 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.

Original Estimate :

Original estimate.PNG

Remaining Estimate :

Remaining estimate.PNG

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).

Image.jpeg

 

Please help me on this issue.

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 7, 2020

You should remove the (sprint) estimates from the sub-tasks, they are ignored by velocity as they're not relevant to your sprint commitments.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events