Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

I think I broke Jira's Sprint Reporting :|

Hi all,


Our company's using Jira cloud and we recently switched to Scrum (from Kanban).

In the past 2 + current sprint, we noticed that the built in SPrint reporting only reports the forecasted (committed) story points but the "done" ones were not being reported.

This means the burndown and velocity charts will always show "0" completed stories but if you manually extract the data in jira (sum up all the story points for issues completed within the sprint duration), you will get numbers.

Any general suggestions where I should take a look?


Thanks in adv.


Take a look at your Board settings -> Estimation and validate Estimation Statistic is Story Points.

And check to make sure the Done/Closed status is on your board as a Column

Like # people like this

Aslo, I forgot to ask if you are using the JIRA Standard Project (Company Managed Project) or Next-Gen (Team Managed Project). They may be different configurations.

Like # people like this

Kathi. Your second suggestion helped me.

The Estimation statistic is indeed "Story Points"

There's definitely a "Done" column.


In my effort to make it more "burdensome" to cancel issues (by dragging htem over to the "Cancel") column, I positionined the Canceled column AFTER done.

When I switched their positions, that fixed the reporting. Now I'm seeing the velocity/burndowns reporting "Done" tickets. :|

Huuuuge Thanks!!! :)

Like # people like this

Just to be clear in case someone else lands here - the important bit for your sprint is that burn-down only happens when an issue is "done".  Jira defines this as "in a status that is in the last column on the board". 

It doesn't care what the status is, what the status category is (although that matters in the sprint report gadget), or what the resolution is.  Only "in the last column" matters.

Like # people like this

@Nic Brough That is great info, thank you!

Like Monika Marko likes this


Log in or Sign up to comment

Atlassian Community Events