Issue #1 - Stories/Issues listed in the Sprint Start - lets say Sprint 2, are closed out on Day 2 of Sprint 2, yet the Burndown data does not show that? the only reference to the story/issue is defined as "Sprint Start" - there is no "Issue Completed" recorded in the data, and there is no decrements of the story points delivered? When you look at the story, it is closed, and it was closed in the current sprint.
This Sprint started on 1/28, xxxx-3750 was scheduled in Sprint 2 from the start, and was closed out on 2/4, 8 days into a 14 day Sprint - I pulled this data on day 9... I have other examples of this occurring for this team and one other? What is causing this?
|Issue||Event Type||Event Detail||Inc.||Dec.||Remaining||Type||Status|
|xxxx-3750||Sprint start||Sprint start||0||Story||Closed|
Issue #2 - Items that are included in the Sprint, albeit at "Sprint Start", with a story point value of '0' - are later updated in the same Sprint with a new story point value - of lets say '5' - the Burndown data created a line item called "Estimate of 5 has been added" however the nothing incremented by '5'??? can this be explained? The Story, when viewed has 5 story points listed. What is causing this?
|Date||Issue||Event Type||Event Detail||Inc.||Dec.||Remaining|
|1/28/2020 20:25||xxxx-13041||Sprint start||Sprint start||-|
|1/30/2020 1:30||xxxx-13041||Scope change||Estimate of 5 has been added||0||50|
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