Carry Unfinished Shortcut Stories into the Next Iteration
Use the Shortcut Iterations Manage page to move unfinished Stories into the next Iteration. Dragging between Iterations moves the work instead of creating duplicate Stories.
Iterations must be enabled in Settings > Features. Have the next Iteration ready and agree which open Stories still belong in the next commitment.
Example: Sprint 24 ends with a payment retry Story in progress and a research Story no longer needed. Carry the retry work forward; leave a clear disposition for research rather than copying both automatically.
Step-by-step guide
Inspect the ending Iteration
Open its detail page and review remaining Stories, owners and blocked relationships. Separate work worth continuing from work that should return for reprioritization.
Confirm the next timebox
Open Iterations from the left navigation. Identify the destination by Team and date range; a similarly named Iteration belonging to another squad is a common selection error.
Move continuing Stories
On Iterations Manage, drag each selected unfinished Story from the ending Iteration to the next one. Keep the original Story so discussion and development associations remain attached.
Recheck the commitment
Open the next Iteration and inspect the moved Stories and progress totals. Review owners and estimates before adding fresh scope; use the ended Iteration reports for retrospective context.
Common mistakes
Duplicating unfinished work
A duplicate produces a new Story and separates its history. Move the existing Story when the work is continuing.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.