Jira Sprint Completion: A Step-by-Step Process and Checklist
Searching for jira complete sprint steps? Follow this checklist to close your sprint and handle unfinished work correctly. Read now.
An unfinished sprint can make a team’s progress hard to interpret. If you close it too early, incomplete work may disappear from the active sprint, reports can tell the wrong story, and the next sprint may start with unclear priorities.
That uncertainty grows when people don’t know what Jira does with unfinished issues or which permissions are needed. A rushed click can turn a routine sprint handoff into extra cleanup for the whole team.
Here’s the truth: completing a sprint is straightforward when you review the work first, agree on what counts as done, and check the destination for anything unfinished. I’ll walk you through the Jira steps, a practical completion checklist, and ways to make sprint transitions more reliable.
How to Complete a Sprint in Jira
To complete a sprint in Jira, open the active sprint on your board, review its issues, choose Complete sprint, decide where unfinished issues should go, and confirm. Check the sprint report afterward to verify the result.
Here’s why the review matters: Jira moves incomplete issues out of the completed sprint. Depending on your choices, they may go into the backlog or another sprint. Confirm the destination with your team before you finish.
-
Open the active sprint. Go to the Scrum board that contains the sprint you want to complete. Open the board’s active sprint view, then check the sprint name and dates.
If you can’t see the sprint controls, confirm that you’re on the correct board and have permission to manage sprints. Board settings and Jira versions can change the exact location of controls.
-
Review the work in the sprint. Look through each issue and check its current status. Confirm which items meet your team’s definition of done, and flag blocked work or work still in progress.
For example, a feature marked complete may still need a review or test. Agree on whether that work meets your team’s completion criteria before closing the sprint.
-
Resolve issues that need attention. Update statuses, add a clear comment, or ask the relevant teammate to confirm the issue’s state. Make sure completed work is represented accurately on the board.
Don’t change an issue’s status just to make the sprint look finished. Accurate statuses give your team a more useful sprint report and a clearer handoff.
-
Choose the sprint completion control. Select Complete sprint from the active sprint view. Jira may prompt you to decide what should happen to incomplete issues.
Pause before confirming. Check that the sprint shown in the prompt is the one you intend to close.
-
Choose where incomplete issues go. Depending on your Jira setup, you may be able to move unfinished work to the backlog or another sprint. Select the destination your team agreed on.
For instance, send a blocked issue to the backlog if it needs fresh prioritization. If the team has already committed to continue it, moving it into the next sprint may make more sense.
-
Confirm the completion. Review Jira’s summary of the changes and confirm the action. Jira completes the sprint and moves unfinished issues according to your selection.
If a confirmation screen shows unexpected issues or a surprising destination, stop and review the choices. You can correct the plan before confirming.
-
Check the sprint report and next steps. Open the completed sprint’s report and review completed and incomplete work. Confirm that moved issues appear in the expected backlog or sprint.
Share the outcome with your team, then plan the next sprint when appropriate. A short review can catch a misplaced issue before it becomes a planning problem.

Pre-Completion Checklist for a Clean Sprint Handoff
A quick checklist helps you finish a sprint without losing track of unfinished work. Use it before selecting the completion control, especially when several teammates own issues.
- Confirm the board and sprint name.
- Check the sprint’s planned end date and team expectations.
- Review every issue’s status and owner.
- Confirm completed work meets your definition of done.
- Identify blocked or incomplete work that needs a decision.
- Agree whether unfinished issues belong in the backlog or another sprint.
- Check that the next sprint is ready if you plan to move work there.
- Review the sprint report after completion.
The best part? You don’t need a lengthy meeting for every sprint close. A quick owner check on two or three unfinished issues can be enough to prevent confusion.

What Happens to Unfinished Issues?
Jira removes incomplete issues from the sprint when you complete it. You’ll generally choose whether that work returns to the backlog or moves into another sprint, depending on your board and Jira configuration.
Consider a team with one unfinished testing task and one feature that has lost priority. The testing task might move into the next sprint if the team has capacity. The deprioritized feature may be better placed in the backlog for a later decision.
Let me explain: sprint completion records what the team finished during that sprint. Moving an issue doesn’t mean the work is complete; it changes where the team will manage it next.
How to Read the Sprint Report After Completion
The sprint report helps you review what the team planned, completed, and carried forward. Use it to check whether the sprint closed as expected, rather than treating the completion message as the only confirmation.
For example, compare the completed issues with the work the team expected to finish. If a task moved out of the sprint, confirm its next location and owner. A moved issue without an owner can easily be overlooked during planning.
Use the report as a conversation aid. Ask what blocked progress, whether the work was estimated appropriately, and what could improve the next sprint. Keep the discussion focused on useful changes rather than blame.
Common Sprint-Closing Mistakes to Avoid
Small oversights at sprint close can create avoidable work later. These are common problems and a practical way to address each one.
- Closing the wrong sprint: Check the board and sprint name before confirming. This is especially important when several boards have active sprints.
- Moving all unfinished work into the next sprint automatically: Review each issue first. The backlog may be the better destination for work that needs reprioritization.
- Marking work complete too soon: Apply your team’s definition of done. If review or testing remains, keep the issue’s status accurate.
- Skipping the report review: Open the sprint report and verify the issue totals and destinations. This catches unexpected changes while the handoff is fresh.
You might be wondering: what if your team disagrees about an unfinished issue? Record the decision and its owner, then revisit the issue during planning. A clear next step is more useful than a rushed status change.
Jira Sprint Management with ONES.com
ONES.com brings project management and knowledge management together, with ONES Project for project management and ONES Wiki for knowledge management. The products are sold separately, so you can choose the capability that fits your team.

ONES Project is a Jira alternative for teams that want sprint management, Jira-compatible workflows, and reporting in a platform that also supports self-hosted deployment. Native capabilities can help reduce reliance on extra plugins.
Core Capabilities
- When sprint transitions need clearer ownership: ONES Project includes sprint management, helping teams organize planned work and manage the next cycle.
- When existing Jira processes are difficult to replace: Jira-compatible workflows help teams carry familiar ways of working into an alternative project management platform.
- When teams need more control over how work moves: Custom workflows let teams adapt issue progress to their own processes.
- When standard issue details don’t capture team needs: Custom fields provide room to track relevant information in project work.
- When teams need visibility into delivery: Built-in reporting gives teams reporting capabilities without requiring a separate reporting add-on for every need.
- When repeated actions consume time: Automation can handle recurring workflow tasks and reduce manual follow-up.
- When plugin dependence adds maintenance: Native project management capabilities can reduce the number of plugins a team needs for everyday work.
- When deployment requirements are strict: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Its cloud and self-hosted versions have full feature parity.
Application Scenarios
A software team replacing Jira: A team can use ONES Project’s Jira-compatible workflows while maintaining sprint management and built-in reporting. Custom fields and workflows can reflect the team’s existing issue-tracking practices.
An organization with restricted networks: A team that cannot use a public cloud service can consider On-Premise, Private Cloud, or Air-gapped deployment. The available deployment choices support different operational requirements.
A team connecting project work with knowledge management: A team can select ONES Project for project management and add ONES Wiki separately for knowledge management. This gives it options as its needs develop.
ONES.com offers a free plan for up to 30 seats. If you’re comparing platforms, check which product you need, the deployment model that fits your environment, and whether its workflows match your team’s process.
Common Challenges When Completing a Sprint
- You can’t find the completion option. Confirm that you’re viewing the active sprint on the correct Scrum board. If the control is still missing, check your permissions or ask a board administrator to review them.
- Unfinished issues are assigned to the wrong place. Decide on the destination before closing the sprint. Review each issue individually when its priority or next owner is uncertain.
- The sprint report doesn’t match your expectations. Check issue statuses and sprint membership. Correct inaccurate details where possible, then review the report again.
- The team closes the sprint without agreeing on what counts as done. Define completion criteria before the sprint starts. For example, specify whether testing and review must be finished before an issue is considered complete.
Frequently Asked Questions
Can I complete a Jira sprint before its end date?
Jira may let you complete an active sprint before its planned end date, depending on your permissions and setup. First check why the team is closing it early and agree on how to handle remaining work. Then review the sprint and its unfinished issues before confirming. If work is still in progress, choose a clear destination so it remains visible after the sprint closes.
What happens if I forget to move unfinished issues?
Jira prompts you to handle incomplete issues when you complete a sprint. The available choices can depend on your board and configuration. Review the prompt carefully and confirm where each unfinished issue should go. After completion, check the sprint report and the selected destination to make sure the work remains visible to the team.
Can I reopen a completed sprint in Jira?
Jira generally treats sprint completion as a completed action, and reopening options can vary by setup and permissions. If you closed the wrong sprint or moved issues incorrectly, check your board and available sprint controls. You may be able to correct the issue locations directly. Ask a Jira administrator for help if your permissions or configuration prevent the correction.
Do I need to start the next sprint immediately?
No. Completing one sprint and starting another are separate actions. Your team can review the completed sprint, refine the backlog, and plan the next cycle before starting it. For example, a team might use a short review meeting to confirm priorities and capacity, then begin the next sprint once its goal and work are clear.
Conclusion
To complete a sprint in Jira, review the active sprint, verify issue statuses, decide where unfinished work belongs, confirm the action, and check the sprint report. That sequence keeps the handoff visible and gives your team a better starting point for its next planning session.
If you’re closing a sprint now, use the checklist before confirming. When your team needs a different project management setup, ONES Project is a Jira alternative with sprint management, Jira-compatible workflows, reporting, and several deployment options.