The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Our Velocity Report is showing a bunch of tickets that were moved around BEFORE the Sprint began, but are showing up in the Velocity Report as "Issues removed from Sprint" because they were momentarily in the Sprint during planning but before we began the Sprint itself. This makes our velocity look pathetic, but that's just misleading.
Hi @Mark Stahura -- Welcome to the Atlassian Community!
When a sprint starts on the button press, it does not change the start/end datetimes. So if those had values earlier than your sprint planning, the changes you note would be included.
Please check to see if this is the case which is causing the report to behave as you noted.
Best regards,
Bill
I've fixed this sort of problem with the burndown/burnup charts by simply changing the Start Time of the Sprint. Set the start time to be immediately after the last "pre-sprint" change.
I haven't checked to see if it will change the data shown on the Sprint Report. It's worth a shot, since this is a super easy workaround.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
👋 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...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.