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
4,299,828
Community Members
 
Community Events
165
Community Groups

Burndown Chart and Active Sprint show different story points. Why?

I am seeing different story points in the active sprint than I am in the burndown chart for the same sprint. I don't know why.

The active sprint shows 10 issues with story points, 24 in total. The burndown chart for this sprint shows 8 issues with story points, 20 in total. Why are these different? What am I missing?

Please see the attached screenshots for additional detail.

 

SP_on_active_sprint-2.pngsp_in_burndown_chart.png

3 answers

@Jason Hayman Did you ever get a resolution for this?  I'm currently experiencing this issue and was wondering if you got an answer from Atlassian.

I did not get any satisfying answers. It's been a while, but I don't think I ever submitted this to Atlassian. I moved on and don't recall encountering it again. Maybe it is a rare bug or simple anomaly.

Thanks for the direction, @Nic Brough _Adaptavist_ 

I compared 4553, which is not in the burndown, to 4931, which is in the burndown. They have the same issue type, same status; I can't find any difference.

And I compared 3285, not in the burndown, to 5039, is in the burndown. They are the same issue type. Status was the same for this screenshot, but different now. I don't see any difference here either.

Any other ideas to investigate?

I'm a bit stuck.  There should be something on the issues which is making them be deselected on the board.

A bit more debugging/long-shots

  • Does a search for Sprint = "Teams Sprint 2020.25" return 10 or 12 issues?
  • Do all 12 issues appear on the active board?
  • Are there any quick-filters on the active sprint board?
  • The search returns all 12 issues.
  • All 12 issues appear in the active sprint and in the backlog view. Two are missing from the burndown chart.
  • There are no quick filters on in the active sprint. That wouldn't affect the burndown chart anyway, would it?

I'm stumped, too. I think I'll send this in to support. I do appreciate the help, @Nic Brough _Adaptavist_ Any other ideas are welcome, though.

Quick filters were a total long shot, they should have nothing to do with it, exactly as you suspect.

With the index tests (search and board), I can't think of anything that could be dropping the two issues from the chart.

0 votes

What are the issue types and status of the two missing issues?

Could you compare 4553 with one that is going into the chart ok (I picked that because it looks like it might be very similar to some of the others, so it might be easier to spot a difference)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

15,019 views 37 49
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