Add or move multiple tickets to a Jira sprint
Open the Jira backlog to add existing tickets to a sprint or move a selection between sprints. Select the work, then drag it into the destination sprint or use its move action. When a sprint is ending, use Complete sprint to roll unfinished work forward instead. Dragging cards between status columns on the active board changes status, not sprint. Choose the right action, then follow the walkthrough for your board type.
Move tickets to sprint
Use the company-managed backlog to move several work items together. Drag them into the target sprint section, or use the selected items’ move action. Adding work to an active sprint requires ranking to be enabled and Schedule work item plus Edit work item permissions.
-
Go to Backlog, not the board
From your sidebar, select Backlog. Find the existing work items in the backlog or their current sprint. -
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.
Use the team-managed backlog to select and move work together. Make sure the Sprints feature is enabled and that the destination sprint appears in the backlog. This route uses dragging or the selected items’ move action; it does not require the bulk-change wizard.
-
Go to Backlog, not the board
From your sidebar, select Backlog. Find the existing work items in the backlog or their current sprint. -
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.
Add tickets, move work, or finish a sprint?
These actions solve different planning problems. Adding work to a sprint does not start the sprint, and changing a ticket’s sprint does not change its workflow status.
| Your task | Where to work | What changes |
|---|---|---|
| Add existing backlog tickets to a sprint | Select the tickets in Backlog and choose or drag to the target sprint. | Their sprint assignment changes. They keep their workflow status. |
| Move selected tickets between sprints | Select work inside the current sprint’s backlog section and move it to the destination. | Only the selected work changes sprint. Active-sprint changes affect scope reporting. |
| Roll unfinished work forward at sprint end | Use Complete sprint and review the destination for incomplete work. | The sprint closes and unfinished work goes to the selected backlog or sprint. |
| Remove selected work from a sprint | Select the work in Backlog and use its move action or drag it to the backlog list. | The work returns to the backlog without being deleted. |
Before you move work to a sprint
Check that the destination is an active or future sprint and that it appears in the backlog you are using. On company-managed boards, adding work to an active sprint requires ranking plus Schedule work item and Edit work item permissions. Ask an admin to check permissions if the action is unavailable.
On team-managed software spaces, enable the Sprints feature before looking for sprint sections. Closing or managing a sprint is a different permission check from editing one ticket. Completing a company-managed sprint requires Jira admin access or Manage Sprints permission; check this before trying to finish it.
Review the selected ticket count and destination name before applying the move. For example, moving three selected tickets into a planned sprint should leave their status unchanged. If you move them into an active sprint, expect the scope change to appear in the relevant reports.
Move unfinished work when completing a sprint
Use Complete sprint when the sprint is ending, rather than manually moving every open ticket first. Review which items Jira considers complete and which remain unfinished, then choose the backlog or an available destination sprint for the unfinished work and confirm completion. For company-managed sprints, complete the subtasks before closing; an unfinished parent can still move to the backlog or a future sprint.
On team-managed boards, work in the last column is considered complete; work in other columns remains incomplete. Check the column mapping before closing the sprint so an item’s apparent status does not lead to an unexpected rollover.
For example, if two items remain in Review at sprint end, decide whether they belong in the next sprint or should return to the backlog for reprioritisation. Closing the sprint with that destination keeps the decision explicit. If a company-managed sprint is shared across boards, review its work on the relevant board before completing it; carryover can depend on the board used to close the sprint.
Return selected tickets to the backlog
Open Backlog and select the tickets inside their current sprint section. Drag the selection into the backlog list, or use the selected items’ move action and choose Backlog. Check that they appear in the backlog afterward.
Returning work to the backlog does not delete it or mark it Done. Removing it from an active sprint is still a scope change, so agree the change with the team rather than using it to make the sprint report look better.
If the sprint or move action is missing
No sprint sections? Confirm you are in Backlog on a Scrum board, or in a team-managed software space with Sprints enabled. A Kanban workflow does not provide the same sprint-planning sections.
Destination missing? Check that the sprint is open and that you are using the intended board or backlog. Board filters and permissions can affect which work and sprints appear. Completed sprints are not valid destinations for these moves.
Cannot move the selection? Check Edit work item and Schedule work item permissions for the relevant company-managed work. Try one known item to distinguish a permission problem from a selection that includes work you cannot change.
Bulk edit asks for a number? That route uses a sprint ID rather than just a name. The sprint ID is available in its backlog URL; use the backlog move action if you prefer to choose the destination visually. See the bulk-edit guide for the separate search-based procedure.
Good to know
A few things worth knowing before you move tickets between sprints:
- Status and sprint are different changes. Dragging a card between status columns changes its workflow status. Use the backlog walkthrough to change the sprint for a selection. The separate bulk-edit route can also update the Sprint field.
- 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.
- Check shared sprints before moving work. In company-managed Jira, sprints can appear across boards and include work from multiple spaces. The board filter and your permissions affect what you see and can change. Do not assume that a sprint name belongs exclusively to the space you are viewing.
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.