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

Epic burndown shows incorrect prediction

Epic burndown prediction display:

- 38 story points remaining

Screenshot 2022-05-26 at 11.13.37.png

Calculate remaining story points manually = 32 points. 


Any ideas?

1 answer

0 votes

Hello @Rochelle Levy ,

It sounds like you are running into an issue with scope change, this is mentioned in the documentation:


Scope change is not considered when calculating the velocity*, but is included in the total work remaining.

So I would recommend looking for any occurrences of scope change where any issues that do not have a value for the 'Estimate' field when a sprint is started and have values entered after the start of the sprint will be treated as scope change.  They show with a * ("Issue added to sprint after start time") next to them in the Sprint Report. and the Burndown Chart records this as a scope change with 'Issue added to sprint' in event detail.


Suggest an answer

Log in or Sign up to answer
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...

14,834 views 37 48
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