shuffling-projects

To move work items between sprints without breaking dependencies, specify explicit source and destination targets while enabling optional dependency updates to relocate any linked blockers alongside the moved items.

Yes, you can preview sprint re-planning changes before committing them by running a dry-run preview, which validates the item movement and dependency relocation outcomes without applying actual modifications to your projects.

When balancing workload across projects, you can apply status filters, priority filters, and unassigned constraints to target specific work items, or optionally provide explicit item IDs for precise control over relocated tasks.

Yes, rebalancing work across sprints supports release rescheduling scenarios by allowing you to move work items between projects or releases while preserving the dependency chains critical to release integrity.

To relocate uncompleted items from one sprint to another, set the source and destination sprints as targets, apply a status filter for uncompleted items, and enable dependency updates to preserve any existing blocker relationships.