I agree with you what you are saying. But let me explain my situation first, the workflow is that the defects go for internal testing from Ready for QA to In Testing and finally to Ready for UAT where client has to test the issues(stories mainly). 99% of the cases the stories are closed and defects are raised against the stories which can be further linked to the concerned story. So, 99% probability is that developers have not to work on the stories. The defects whatever are raised during UAT testing can be moved to new or upcoming sprint. So, if I don't close the sprint as there is a lag between the development and testing, I won't be able to get the actual velocity.
Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot