So I believe this is the workflow that's happening:
1. Start sprint
2. Stories are later pulled in that are not estimated
3. Stories are estimated
4. Stories are completed
5. Jira shows - where estimate should be for said completed stories
6. Points are not reflected on velocity though they were completed durint the sprint
Scope was increased and the burndown reflects this when the estimates were entered but the velocity does not show the added work that was completed. Though I agree this should not be added to the intial commitment of the sprint number, it should be counted in the velocity as stories that were finished.
Is this a feature or a bug? If it is a feature, is there any way to turn it off?
Seems like this is talking about the same issue: https://answers.atlassian.com/questions/243034/stories-effort-added-after-sprint-started-not-in-sprint-reportand it doesn't look like there is a great answer...
Hello all! What have you learned from your customers lately? Our live-streamed series continues by exploring CX, UX, and the power of research & insights at scale with Leisa Reichelt, Head of R...
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