Jira Sprint Completion: A Step-by-Step Guide and Checklist
Need help to complete a Jira sprint without losing track of unfinished work? Follow this step-by-step guide and checklist. Read now to close with confidence.
A sprint can end with finished work, unfinished tickets, and a team unsure what Jira will do next. If you click the wrong control or overlook carryover work, your board may not reflect what the team agreed to deliver.
That uncertainty can muddy sprint reporting and make the next planning meeting harder. But here's the truth: completing a Jira sprint is straightforward when you review the scope, choose where unfinished issues go, and check the outcome. Here’s a step-by-step process, plus a practical checklist to help you close the sprint without losing track of work.
How to Complete a Sprint in Jira
To complete a sprint in Jira, open the active sprint on your Scrum board, review its issues, select the sprint completion control, decide where unfinished issues should go, and confirm. Check the sprint report afterward to verify which work Jira counted as complete and what carried over.
- Open the correct Scrum board. Go to the board that contains the sprint you intend to close. If your team has several boards, confirm the project and sprint name before making changes.
- Review the sprint’s work. Scan completed, in-progress, and not-started issues. Check each issue’s status and assignee, and ask the team to flag work that needs a decision.
- Agree on the sprint outcome. Compare delivered work with the sprint goal. Decide whether unfinished issues should move to the backlog or into another sprint, if Jira offers that choice.
- Select the completion control. On the board’s active sprint view, choose Complete sprint from the sprint controls. The label or location can vary slightly between Jira versions.
- Choose what happens to unfinished issues. In the confirmation dialog, select the destination available to your board. Review the selection before proceeding; carryover issues should remain visible for future planning.
- Confirm and inspect the result. Complete the sprint, then open its report. Check the completed work, incomplete work, and any issues moved elsewhere.
For example, if a sprint has eight finished issues and two unfinished ones, you can close it and move the remaining work to the backlog for discussion during the next planning session.

What to Check Before You Close the Sprint
A quick review before closing can prevent confusion later. Start with the sprint goal, then look at the issue statuses and any work that is still underway.
Check that the team agrees on which issues count as complete. Jira’s sprint report relies on the board’s column and status setup, so a status that looks finished to a teammate may not be treated as complete if the board maps it differently.
- Confirm the sprint name and board.
- Review the sprint goal and the work delivered.
- Identify issues that are not complete and agree on their next destination.
- Check that finished work appears in the board’s completed column.
- Tell the team when the sprint will close, especially if someone is still updating an issue.
Here's why: an issue’s status is more than a label. If a team uses a custom status such as “Ready for release,” check how it maps to the board before relying on the sprint report.
What Happens to Incomplete Issues?
Completing a sprint does not automatically finish every issue inside it. Jira asks you to handle unfinished issues, commonly by moving them to the backlog or another sprint, depending on your board and Jira setup.
Imagine a developer has started a feature, but testing is still outstanding. The team can move that issue to the next sprint or return it to the backlog for prioritization. Either way, the issue remains available for future work.
Carryover can also affect sprint reporting. If the team regularly moves a large share of work forward, review how much work fits into a sprint and whether dependencies or changing priorities are disrupting delivery.
The best part? Carryover is useful information, not a reason to hide unfinished work. Keep the issue visible, explain its status, and make a clear decision about when it should be tackled.
How to Use the Sprint Report After Completion
Once the sprint is closed, open its report and compare the completed work with the sprint goal. Look at the issues Jira classified as complete and the issues it recorded as incomplete or carried forward.
For example, if the team planned ten issues and completed seven, ask what shaped the result. Were three issues blocked by an external dependency, or did new work enter the sprint midway through? The answer can guide a specific change in the next planning session.
Use the report to support a conversation, not to assign blame. A small number of unfinished issues may reflect a sensible decision to protect quality, while repeated carryover could point to oversized estimates or unresolved dependencies.
Let me explain: the report is most helpful when the team agrees on what it means. Check how your board maps statuses and discuss any issue that appears in an unexpected category.
A Sprint Completion Checklist for Your Team
Use this checklist during the final review. It works especially well when the team follows the same order each sprint, because everyone knows when to raise blockers and make carryover decisions.
- Goal: The team has reviewed whether the sprint goal was met and recorded any important context.
- Issues: Completed work has the right status, and unfinished work has an agreed next step.
- Board: The active sprint and destination for carryover issues are correct.
- Team: Relevant teammates know the sprint is closing and have had a chance to update their issues.
- Report: The team has checked the sprint report for unexpected classifications or missing work.
- Follow-up: Blockers and improvement ideas have an owner or a place in the next team discussion.
You might be wondering: does every issue need to be complete before you close a sprint? No. The important thing is to handle unfinished work deliberately and keep its next step clear.
ONES.com Solution for Managing Sprint Work

Value Proposition
ONES.com brings project management and knowledge management together in one platform, while ONES Project and ONES Wiki are sold separately. Teams can use ONES Project to manage sprint work and ONES Wiki to keep team guidance and project knowledge accessible.
Core Capabilities
- Disconnected sprint work: ONES Project provides Jira-compatible workflows, helping teams manage familiar issue processes in a Jira alternative.
- Hard-to-track progress: Built-in reporting gives teams a clearer view of sprint activity and delivery progress.
- Rigid issue processes: Custom workflows let teams shape work stages around their own review and delivery practices.
- Fields that do not fit: Custom fields let teams capture details relevant to their projects without relying on a fixed set of attributes.
- Manual sprint planning: Sprint management supports planning and tracking work across development cycles.
- Repeated routine tasks: Automation can reduce manual steps in recurring project workflows.
- Scattered team guidance: ONES Wiki gives teams a knowledge management option for organizing guidance alongside project work.
- Plugin-heavy setups: Native project capabilities can reduce reliance on extra plugins for common workflow and reporting needs.
- Deployment restrictions: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments, with feature parity between cloud and self-hosted versions.
Application Scenarios
A development team moving from Jira: A team that needs a Jira alternative can map familiar workflows in ONES Project, configure its own fields, and use built-in reporting to review sprint progress.
A team in a restricted network: An organization with strict hosting requirements can assess the self-hosted deployment options, including Air-gapped, while retaining feature parity with the cloud version.
A team improving project handoffs: A group can manage sprint tasks in ONES Project and keep process guidance in ONES Wiki. Since the products are sold separately, the team can choose the one that fits its needs.
ONES.com offers a free plan for up to 30 seats. Check deployment, workflow, and knowledge management requirements when deciding whether the platform suits your team.
Common Challenges When Completing a Sprint
Unfinished issues have no agreed destination
Problem: Team members expect an issue to move to different places, so it becomes hard to find during the next planning cycle.
Solution: Agree whether the issue belongs in the backlog or a future sprint before confirming completion. Make its priority and next action clear.
Jira shows work as incomplete unexpectedly
Problem: A team member believes an issue is finished, but the sprint report lists it as incomplete.
Solution: Check the issue’s status and the board’s column mapping. Update the status or board configuration through the appropriate team process, then review the report again.
The sprint goal is overlooked
Problem: The team closes the sprint by counting issues alone, without checking whether the intended outcome was delivered.
Solution: Revisit the goal during the closing review. Record what changed, including scope decisions or blockers, so the next planning discussion has useful context.
Team members are still changing issues
Problem: Someone updates an issue while another teammate is closing the sprint, creating uncertainty about its final status.
Solution: Set a clear closing time and ask the team to finish status updates beforehand. If a late change is necessary, confirm the resulting issue status after the sprint closes.
FAQs About Completing a Jira Sprint
Can I complete a Jira sprint with unfinished issues?
Yes. You can close a sprint even when some issues are unfinished. Jira prompts you to decide what happens to that work, with options that commonly include moving it to the backlog or another sprint. Review the destination carefully and make sure the team knows what to pick up next.
What happens to unfinished issues when I complete a sprint?
Jira does not turn unfinished issues into completed work. Depending on the board and available choices, you can move them to the backlog or a future sprint. They remain available for prioritization and further work. Check the sprint report after closing to confirm how each issue was handled.
Why does Jira show an issue as incomplete when it looks finished?
The issue’s status may not map to a completed column on the board. Check the status and board column mapping, especially if your team uses custom statuses such as “Ready for release.” A mismatch can affect how Jira classifies the issue in the sprint report, even when the team considers the work done.
Can I reopen a completed sprint?
Jira’s sprint controls and permissions can vary by version and configuration, so check the options available on your board before assuming a completed sprint can be reopened. If you need to correct an issue or report outcome, first confirm the issue’s status and board mapping. Ask a Jira administrator for help if the controls you need are unavailable.
Should I complete a sprint if the sprint goal was missed?
A missed goal does not necessarily mean you should leave the sprint open. Review what happened, close the sprint when the team is ready to move on, and handle unfinished work deliberately. Record the main blocker or scope change so the next planning discussion can address the cause rather than simply repeating the same plan.
Conclusion
To complete a sprint in Jira, review the active sprint, agree on the outcome, choose where unfinished issues should go, and inspect the sprint report. A short checklist helps the team close work consistently and keep carryover visible.
When sprint completion feels confusing, a clear process can reduce status surprises and make the next planning session more useful. Review the goal, close the sprint with intention, and use what you learn to plan the next cycle more realistically.