nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

My burndown chart considers remaining work from tasks in Done status

Luiz Ferreira_zsyvjh

Currently my burndown chart is based on the remaining work of the stories I own.

What currently happens is that it is considering the remaining work of tasks that are already in the last column of the board.

Example:
A task in the column done has the remaining work of 6h. (I finished it before it was planned).

We have 5 more tasks (2h remaning each) in the column To Do or In Progress.

Our burndown shows the remaning work as 16h and it should be only 10h.

Can you help me, please?

Accepted answers

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

Burndown does not look at remaining work. It looks at what you committed to at the start of the sprint, and burns down the estimate on each issue you complete. It doesn't matter if your estimate was wrong and you completed faster or slower.

You should not set your sprint to look at remaining estimates. Could you confirm what field you are actually using for the sprint estimate?

All comments

Heather Ronnebeck

Hi @Luiz Ferreira

Welcome to the community. Do you happen to have your Done status tickets complete with a resolution or are they just changed to a Done status? The resolution would show beside the Status on the ticket view.

I ask because I think that the burndown reports are showing only resolved tickets as done, so I think it's a good first step to validate the resolutions are being populated first.

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

You should not set your sprint to look at remaining estimates. Could you confirm what field you are actually using for the sprint estimate?

Heather Ronnebeck

@Nic Brough -Adaptavist- I was thinking maybe he was referring to the Epic burndown and not the normal sprint one.

Luiz Ferreira_zsyvjh

Hello @Heather Ronnebeck and @Nic Brough -Adaptavist- , actually I'm looking at my Sprint Burndown, that's true.

I'm using a field called "Original Estimate" to add the estimate effort

Luiz Ferreira_zsyvjh

Hello @Heather Ronnebeck , actually all the items in the "Done" column have a log of resolved. I'm checking to see if I'm not making any mistake.

Nic Brough -Adaptavist-

Thanks for checking that @Heather Ronnebeck - I had not thought of that!

With original estimate set as the sprint estimate, then I have a feeling this is still correct, but I can't be sure given the data you've given us. The problem is that you're looking at remaining estimate, which the burndown does not.

I can fill in the missing bit which will then help me explain. Taking the three issues you've defined:

	Original estimate	Remaining estimate	Status
ABC-1	10	6	Done
ABC-2	3	2	not done
ABC-3	3	2	not done

In this case, I would expect a burndown chart to start the sprint at 16 hours, and show a dip down to 6 hours when ABC-1 moved to "done". The burndown is being done on the sprint estimate, the amount you've actually done is irrelevant.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

burndown