Move multiple tickets to the next sprint in Jira
The Jira board view has no option to move cards to a different sprint. Dragging a card on the board changes its status column, not its sprint, and right-clicking on the board doesn't include a sprint field at all. Sprint reassignment happens in the Backlog. Here's how to do it in both space types.
Choose your Jira board type
Company-managed Jira Team-managed JiraCompany-managed board
Like all Jira space types, company-managed gives you no sprint-move option on the board itself. Sprint changes go through the Backlog. You can drag work items into the target sprint section, or right-click and choose Move work item.
-
Go to Backlog, not the board
The Active Sprints board has no way to move cards to a different sprint. From your sidebar, select Backlog. -
Select multiple work items
Use Shift to select an adjacent range or ⌘ (Mac) / Ctrl (Windows) for individual work items. -
Drag into the sprint, or right-click → Move work item
Drag selected work items directly into the target sprint section in the backlog, or right-click any selected work item and choose Move work item to pick the destination sprint. -
Confirm the scope-change warning
Moving work items in or out of an active sprint is a tracked scope change. Confirm to proceed.
Move sprints from the board
Select work items and move them without opening Backlog.
Team-managed board
The board view in team-managed spaces has no option to change a card's sprint. Multi-select and sprint moves both happen from the Backlog tab. Unlike company-managed, there's no bulk-change wizard: select the work items and use the ··· menu to move them.
-
Go to Backlog, not the board
The board view has no option to move cards to a different sprint. From your sidebar, select Backlog. -
Select multiple work items
Click the first work item, then hold Shift to select an adjacent range, or ⌘ (Mac) / Ctrl (Windows) to pick non-adjacent work items. -
Drag into the sprint, or right-click → Move work item
Drag selected work items directly into the target sprint section in the backlog, or right-click any selected work item and choose Move work item to pick the destination sprint. -
Confirm the scope-change warning
If you're moving work items into or out of an active sprint, Jira flags it as a scope change affecting burndown and velocity reports. Confirm to proceed.
Skip the Backlog detour
Move selected work items to the next sprint directly from the board.
Good to know
A few things worth knowing before you move tickets between sprints:
- Jira's board view has no sprint-move option. Dragging a card on the Jira board changes its status column, not its sprint. Sprint reassignment for any number of cards requires the Backlog view.
- Scope changes are tracked. Moving work items into or out of an active sprint is recorded as a scope change and shows up in the burndown chart and sprint report. If you're rolling over unfinished work, it's cleaner to use the Complete sprint dialog, which asks where incomplete work items should go.
- Closed sprints can't receive moves. Only active and future sprints are valid destinations; Jira excludes completed sprints from the destination list entirely.
- Sprints are space-specific. A work item can only be assigned to a sprint within its own space. Even on a multi-space board, you can't move a work item into a sprint from a different space.
Sprint planning without the backlog detour
BetterBoard treats Sprint like any other field: select cards, set the sprint, done. Free to try with your Jira.
FAQ
Why can't I drag multiple work items to a sprint at once in Jira?
Jira's drag-and-drop is designed for one card at a time. To move several at once, open the Backlog view, Shift- or Ctrl-select the work items, then right-click and choose the target sprint. For very large moves, use the bulk-change wizard via Advanced Search.
How do I move unfinished work items to the next sprint when closing a sprint?
Use the Complete sprint dialog. When you close an active sprint, Jira asks where to send incomplete work items: you can send them all to the backlog or to a specific future sprint in one action. This is the cleanest way to roll work forward.
Why does bulk edit ask for a sprint ID instead of the sprint name?
In company-managed spaces, the Sprint field stored on a work item is a numeric ID. When you bulk-edit it, Jira may ask for that ID rather than the display name. You can find the sprint ID in the sprint's URL when you open it in the backlog.
Can I move work items into a sprint that hasn't started yet?
Yes. Future (planned) sprints are valid destinations. You can only move work items into active or future sprints: closed sprints can't receive moved work items.
Will moving work items into an active sprint mess up my reports?
It's recorded as a scope change, which appears in the burndown chart and sprint report. That's intended behavior so teams can see mid-sprint changes. If you don't want it reflected, plan moves before the sprint starts.
Can I move work items from different spaces into the same sprint?
No. Sprints are space-specific in Jira: a work item can only be assigned to a sprint within its own space. This applies in BetterBoard too. What BetterBoard does let you do is bulk-reassign sprints for work items across multiple spaces from a single board view, without visiting each space's backlog separately.