Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Sprint report for sprint - xx does not show burn down when issues are completed

burndown report.pngwf.pngboard.png

2 answers

0 votes


Make sure that the Resolution field is not empty for the issues.

In this sprint we have:

3 issues in To Do. Resolution unresolved. Story points combined = 10

5 issues in In Progress. Resolution unresolved. Story points combined = 12

7 issuses in Done (completed) and Resolution is set to Done. Story points combined = 8

What can we expect the burn down to show here?

If 7 issues with the resolution done are in the most right column of your board, then you will have 8 story points burn down.

Well, as you can see in the above picture on the burndown - this is not showing this

It could be that you are adding issues after the sprint started and that is why the line does not go down.

OK - I will check with my user on that matter but she says that previous sprints has worked just fine and they have not done anything different on this one.

You can open the Sprint report. There will be a table with all issues. You can see which issues were added after sprint. You can see which issues are considered completed.

This is my sprint report - so what you are saying is that the 8 story point that have been completed will show progress in the first picture - but they do not.

It also seems like there where now issues added after the sprint had started...

There must be a table under the burn down chart, could you paste the screen shot here?

Screenshot 2019-02-15 at 13.36.50.png

OK - I found this and it seems like they have done some changes after all

But not that much...


I am not sure what is wrong. From your screenshots it should work

ok - any suggestions on how I should proceed this?

I would need to have a look at your instance to get more ideas, but it is not possible. Maybe someone else will see the question and say something.

I unmarked this answer as accepted.

OK - if no answer I can raise this as an Atlassian support ticket

In the sprint report.png you can see that we have finished 496, 510, 554, 555, 584.
In table.png you can see that all of these are in the sprint from the sprintstart, this without any Event types has occured, except for 584 (this one has a scope change because its added in the sprint).
In table.png we expext to see a new row for every issue that's finished.
Even in burndown report.png You can see that the line does not drop/change even thought issues are finished.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

312 views 9 7
Read article

Community Events

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

Events near you