I understand that Sprint planning meeting is part of an Sprint, so it suppose that the sprints starts when the Sprint planning meeting is being done. If you do so, setting the start of the sprint to the date and hour when the sprint planning meeting starts, makes your commitment zero when you end the sprint due jira thinks you added issues after th start of the sprint. It shouldn't be like that.
The Velocity Chart (like a number of the reports) work best when sprints are started at the day/time you press the button.
This is because it takes into account what happened prior to the time you start the sprint otherwise - which can discount stories added or estimates.
In reality, the sprint does begin once planning starts - is there a concern with starting it then rather than earlier?
Learn how to use two new reports for next-gen projects in Jira Cloud: Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...
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