When does an iteration (sprint) end?
My team's project has a release and sprints defined.
Today is October 9. According to the Project landing page, Sprint 1 ended on October 8 (yesterday):
However, work item queries filtered for current iteration return work items in Sprint 1, not Sprint 2 as expected.
I've tried moving all open work items out of Sprint 1 and assigning them to Sprint 2, but current iteration still seems to be Sprint 1.
Is this behaving as intended? Should I open a defect?
How do I force a sprint to end?
Today is October 9. According to the Project landing page, Sprint 1 ended on October 8 (yesterday):
However, work item queries filtered for current iteration return work items in Sprint 1, not Sprint 2 as expected.
I've tried moving all open work items out of Sprint 1 and assigning them to Sprint 2, but current iteration still seems to be Sprint 1.
Is this behaving as intended? Should I open a defect?
How do I force a sprint to end?
Accepted answer
Hi Leons,
This is not intended behavior. Sprints are suppose to automatically update based on dates. I will file a bug on this and hopefully, we can resolve it quickly.
In the meantime, as temporary solution, you can change sprint 1 end date to Oct. 7th and this will update your sprints.
Thank you for letting us know.
Fariz
One other answer
Last I saw , YOU must MANUALLY change the 'current iteration' pointer in the project configuration. it will NOT update on its own.
also, there is no formal 'switch' in RTC that indicates end of sprint. It ends when the date says it ends.
'Current' has nothing to do with the state of the sprint.
also, there is no formal 'switch' in RTC that indicates end of sprint. It ends when the date says it ends.
'Current' has nothing to do with the state of the sprint.
Comments
