I'm facing a problem with the Burndown chart.
I've planned my Sprint 3, and after adding ALL the Stories I start it on the 30/08.
The problem is that the burndown chart is showing the stories as if they were added after the sprint start, as Scope change. Even more akward is that it is marking this Scope changes as one per day for future dates always at 6:00.
Attached is the current Burndown chart on the 02/09.
Any idea what is the cause of this behaviour? And own can I solve it?
@Rahul - yes, the estimation was made before the sprint was started. After the sprint is started, all the stories appear in the burndown chart and report as scope change. My burndown chart and report are similar to Nuno's.
In case it is helpful, my board contains issues from two projects. Also, I have parallel sprints labs feature turned on. I am not using parallel sprints on this board, but they are being used in another project / board in my organization.
Hi @Rahul and @Nuno,
I think my issue might have been caused by adjusting the sprint start date right before starting the sprint, from the default time it gives (current time) to an earlier day/time. We tend to start our sprints after planning meeting, which is usually Monday @ noon. However, in the last sprint, the planning meeting went late and we didn't start the sprint in JIRA until Tuesday morning. When I started the sprint in JIRA, I back-dated the sprint start date to the afternoon of the day before (to reflect when developers started working on issues). However, I think it treated all issues as scope change because of that.
Is that expected? @Nuno - did you adjust your start date?
I just started my next sprint, leaving the defaults, and at least initially, it seems fine. I did experience what @Nuno did with an issue appearing to change scope at the same time every day.
This happened for the first time in Sprint 3, and I did in fact adjust the dates (not sure if it was the start or end date, and for before or after). however it happens on the following sprint as well, even if the date weren't changed.
If the problem is with the dates being changes, it seems a bug to me. If the date change functionality is available it shouldn't cause this issue.
Sorry to attempt to revive such an old thread but it's 2016 and this still happens. Basically if you do sprint planning on the first day of the sprint and set the start time to any time before the moment you clicked "Start Sprint" (even an earlier time on the same day), any changes made between the start time set on the sprint and the moment you clicked "Start Sprint" are counted as scope change. This seems pretty crazy. Is there no way to work around this? I've worked with other tools that did not have this problem.
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs