Forums

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

Burndown chart - time spent is 0

Nicolaj Kvejborg Hansen
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!
September 1, 2021

Well the problem is, when I log work on issues, stories og subtask in the current sprint, the burndown chart only records and updates the "remaining time estimation". Time spent is still equal to 0?

 

How can i solve this?

1 answer

0 votes
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.
September 1, 2021

Welcome to the Atlassian Community!

The burn down chart can be set to look at all sorts of numbers, so the first question is "what is the estimation statistic for the board?".  If you are estimating and burning down on Story Points, then logging work will not affect the burndown. 

Once you have worked out what your burndown estimation is (or should be), then you'll need to look at what burndown is.

A burndown counts delivery vs commitment.  An issue is delivered, and its estimate burned-down, when it reaches the "done" part of the process.  In Jira that is "any status in the last column on the board".  So logging work, even if work-logs are the estimation, will have no effect.  What matters is what the estimate was and that the issue becomes "done"

Note that sub-tasks are irrelevant to burn-down as well.  They are not the items you commit to, they are an integral part of their parent issue (which is what you do commit to completing), so the estimates and worklogs on them are irrelevant to burn-down.

Suggest an answer

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

Atlassian Community Events