Burned story point is unsync with actual sprint burn down

[Philip Lau]

Both taken at the same time but the burnt story point of current sprint has a super huge difference.

[Philip Lau]

Settings Just in case you think it is not targeting the same board

[Danut M [StonikByte]]

Hi Philip,

Indeed there is a big discrepancy. Could you please let me know if you use estimates (on Story Points) on sub-tasks? This could be a possible cause because our gadget only considers the parent tasks in the calculation.

Would it be OK to give us a test user so we can login and investigate? If yes, can you please provide these credentials to [e-mail]? Otherwise we will need at least an export in CSV of the data (with these fields Issue Key, Story Points, Resolution, Status, Sprint, Type) that is displayed in Sprint Health Gadget for each of the 3 statuses (Open, In progress, Done) + an export of the filter that our gadget does so we can compare them and see where the discrepancy comes from.

Danut.

[Philip Lau]

I have created an account for you

https://aresgames.atlassian.net Username: testing with email: [e-mail]

[Danut M [StonikByte]]

Thanks Philip. I was able to log on and I think I found the cause of the big differences.

The gadget was configured with End Date = "Sprint End Date", which is the date & time when the sprint was supposed to be finished. But you guys closed the sprint later and all the changes in sprint scope made after the "Sprint End Date" were not reflected in the chart. The Sprint Health Gadget displayed those changes and this caused the big discrepancy.

To fix this, please configure the gadget to use End Date = "Sprint Closure Date". With this setting, if the sprint is not closed yet, you will still get status based on current time/date.

Please try this and let me know if there are still discrepancies.

[Philip Lau]

Cool Thank you very much!