Closed user story and tasks from 9/25 is showing up in 9/26 sprint backlog.

Question

Closed user story and tasks from 9/25 is showing up in 9/26 sprint backlog.

Cindy Combs 0

We have a Closed user story and part of its closed tasks from 9/25 is showing up in 9/26 sprint backlog. Sprint iteration on closed story correctly reflects last year. Why would this be populating in current 2026 sprint?

Tejaswini Billakurthi 270 Reputation points Microsoft External Staff Moderator

2026-09-11T14:58:12.4566667+00:00
Hello @Cindy Combs ,

Thank you for reaching out to Microsoft Q & A !

Sprint backlogs are primarily driven by the team's Area Path and the sprint's Iteration Path. Since the sprint backlog is scoped to the selected sprint, it would be worth checking whether the work items currently carry the 2026 sprint Iteration Path, even if the parent User Story still shows a previous year's sprint.

A few things to check:

Verify the Iteration Path on the child tasks. Tasks are evaluated independently and can belong to a different sprint than their parent User Story. Add the Iteration Path column to the backlog and check which items are assigned to the current sprint.

Review the work item History. If an Iteration Path was changed manually, the History tab will show when it changed and by whom.

Check whether the iteration node was renamed, moved, or deleted. Changes to an iteration node can update the Iteration Path on associated work items.

Once you identify which items currently have the 2026 Iteration Path, the work item History should help determine whether the change came from a manual update or an iteration structure change.

Reference: Create and manage your backlog – Backlog and sprint work item filtering

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.

Your answer

Tejaswini Billakurthi 270 Reputation points Microsoft External Staff Moderator

2026-09-11T14:58:12.4566667+00:00

Hello @Cindy Combs ,

Thank you for reaching out to Microsoft Q & A !

Sprint backlogs are primarily driven by the team's Area Path and the sprint's Iteration Path. Since the sprint backlog is scoped to the selected sprint, it would be worth checking whether the work items currently carry the 2026 sprint Iteration Path, even if the parent User Story still shows a previous year's sprint.

A few things to check:

Verify the Iteration Path on the child tasks. Tasks are evaluated independently and can belong to a different sprint than their parent User Story. Add the Iteration Path column to the backlog and check which items are assigned to the current sprint.

Review the work item History. If an Iteration Path was changed manually, the History tab will show when it changed and by whom.

Check whether the iteration node was renamed, moved, or deleted. Changes to an iteration node can update the Iteration Path on associated work items.

Once you identify which items currently have the 2026 Iteration Path, the work item History should help determine whether the change came from a manual update or an iteration structure change.

Reference: Create and manage your backlog – Backlog and sprint work item filtering

Please "Upvote the Answer" if this information helped you. This will help us and others in the community as well.