How to Reopen a Closed Sprint in Jira: A Step-by-Step Guide
Closed a sprint by mistake? Learn how to reopen a closed sprint in Jira and safely handle unfinished work. Read now for the right next steps.
You closed a Jira sprint, then noticed unfinished work still needs attention. Now the sprint is missing from the active board, and its reports may already reflect the closure. That can make a simple mistake feel like a project emergency.
But here's the truth: Jira generally doesn't offer a standard button to reopen a completed sprint. Trying to force a change can create confusion around sprint history and reporting.
The safest approach is to check what happened, confirm whether the sprint is truly complete, and move remaining work into a new sprint when necessary. If the sprint was closed by mistake, involve your Jira administrator before attempting any technical workaround.
Here's a practical walkthrough for handling both situations. You’ll learn what Jira allows, how to keep unfinished work moving, and how to avoid losing the context your team needs.
How to handle a closed sprint in Jira
Jira typically doesn't let you reopen a completed sprint through the standard board interface. In most cases, the dependable way forward is to create another sprint and move unfinished issues into it.
Before changing anything, check whether the sprint actually closed or whether you’re viewing a different board, project, or sprint. Then use these steps to protect the team’s work and keep reporting understandable.
Confirm the sprint’s status. Open the relevant Scrum board and review the sprint list or the board’s completed-sprint view. Check the sprint name, project, and dates so you don’t mistake another sprint for the one you need.
Review the unfinished issues. Open the closed sprint’s report and identify issues that were incomplete when the sprint ended. Check each issue’s current status, assignee, and sprint field. An issue may have been completed or moved since closure.
Ask why the sprint was closed. If the team intended to finish the sprint, treat its history as complete. If someone closed it accidentally, contact your Jira administrator and explain what happened before attempting changes.
Create a replacement sprint. On the same Scrum board, create a new sprint and give it a clear name, such as “Sprint 24 — Carryover.” Set a realistic start and end date if your team is ready to schedule it.
Move the unfinished issues. Add the relevant issues to the new sprint using your board’s backlog or sprint controls. Check that each issue appears in the intended sprint and still has the right status and owner.
Record the context. Add a short note to the new sprint’s goal or team update. Explain why the work carried over and which issues moved, so reports and sprint reviews make sense later.
Verify the board and reports. Confirm the new sprint contains the correct work and the old sprint remains visible as completed. If anything looks wrong, pause and ask your administrator to review the board configuration.
The best part? This approach lets the team continue without pretending the completed sprint never happened. If closure was accidental and you need the original sprint state restored, ask an administrator to check the options available for your Jira version and setup.

Why Jira treats a closed sprint as complete
Closing a sprint signals that the timebox has ended. Jira then uses that event in sprint reports and board history, including work completed, unfinished issues, and carryover.
For example, imagine a two-week sprint ends on Friday with three unfinished issues. The sprint report records the outcome at closure. Creating a follow-up sprint keeps that history intact while giving the remaining work a clear place to go.
You might be wondering: can an administrator simply change the sprint back to active? Jira’s standard interface does not provide a general reopen control. Technical workarounds may depend on Jira’s version, permissions, and configuration, so don’t assume an API change is safe or supported for your environment.
If the sprint was closed only moments ago, avoid making additional changes until an administrator has reviewed it. A quick review can help distinguish an accidental closure from a board or permission issue.
Move unfinished work without confusing sprint reports
Moving an issue into a new sprint is usually clearer than trying to erase the original sprint’s history. The closed sprint still shows what happened, and the replacement sprint shows where the team plans to continue.
Suppose an issue called “Update checkout flow” remains in progress at sprint end. Keep its issue details and status intact, move it into the next sprint, and note why it carried over. That gives teammates context without rewriting the prior sprint’s outcome.
Before moving issues, check whether any have already been assigned to another sprint. Confirm that the new sprint belongs to the correct board, especially if your project uses multiple Scrum boards with different filters.
After the move, review the backlog and the new sprint view. A simple issue count can help you catch an item that was overlooked or added twice.
What to do if you closed the sprint by mistake
First, pause. Don’t delete issues, change sprint fields in bulk, or try an unfamiliar script. Those actions can make it harder to understand what changed and may affect reports or other teams’ work.
Tell your Jira administrator which sprint was closed, when it happened, and whether any issues have since moved. If your organization has a Jira support process, follow it before attempting a technical correction.
Ask the administrator to confirm whether your Jira version and configuration offer a supported way to restore the sprint’s active state. If not, create a replacement sprint and move the unfinished issues. Add a clear note that the earlier sprint was closed accidentally.
For example, a short note such as “Sprint closed early; remaining work moved here” is more useful than silently changing dates or sprint fields. The team can then interpret historical reports with the right context.
Prevent accidental sprint closure next time
A short end-of-sprint routine can prevent many closure surprises. Before selecting the completion control, have the scrum master or sprint owner check the sprint goal, open issues, and any work that needs to carry forward.
It also helps to tell the team who is responsible for ending the sprint. If several people manage the board, agree on a simple signal, such as a review in the team channel before closure.
For example, a team might check the remaining issue count during its final stand-up. If three issues are still in progress, the team can decide whether to complete the sprint as planned and move them forward, rather than closing it without discussion.
Keep sprint names and goals specific enough to distinguish one timebox from another. Clear names make it easier to find the right report if someone later needs to investigate an accidental closure.
ONES.com as a related project-management option
ONES.com combines project management and knowledge management in one platform. ONES Project is the project-management product and a Jira alternative; ONES Wiki provides knowledge management as a Confluence alternative. They are sold separately.

For teams comparing how they manage sprint work, the relevant question is whether the platform supports the workflows, reporting, and deployment conditions they need. ONES.com offers Jira-compatible workflows and self-hosted deployment options, which may matter to organizations with specific infrastructure requirements.
Core capabilities
Work is scattered across different processes: ONES Project supports custom workflows and fields, helping teams organize issue details around their own delivery process.
Teams need familiar Jira-style work patterns: Jira-compatible workflows can make it easier to carry established project practices into a different platform.
Sprint work needs clearer tracking: Sprint management helps teams plan and follow work within iterative delivery cycles.
Project progress is hard to review: Built-in reporting gives teams a way to monitor project activity without relying on extra reporting add-ons.
Repeated administrative work takes time: Automation can handle routine actions, reducing manual effort for recurring workflow tasks.
Teams depend on multiple plugins: Native capabilities can reduce the need for plugins when the required functions are available in the platform.
Hosting requirements differ: ONES.com is available in Cloud, On-Premise, Private Cloud, and Air-gapped deployments, allowing organizations to match deployment to their environment.
Teams need consistent features across hosting choices: The cloud and self-hosted versions have full feature parity, so teams can choose a deployment without giving up feature availability.
Application scenarios
A software team that already uses Jira-style workflows could evaluate ONES Project if it wants sprint management, custom workflows, and reporting in a platform with on-premise deployment. It can compare the actual workflow fit before deciding whether a change is worthwhile.
An organization that also needs a knowledge base can consider ONES Wiki separately from ONES Project. Both products are part of ONES.com, but teams can purchase them separately and choose the capabilities that suit their needs.
ONES.com offers a free plan for up to 30 seats. For a team reviewing alternatives, a practical evaluation should include sprint planning, issue transitions, reporting, deployment needs, and the amount of plugin dependence in its current setup.
Common challenges when dealing with a closed sprint
The sprint is missing from the active board
Problem: A completed sprint no longer appears with active work, so teammates assume its issues have disappeared.
Solution: Open the completed-sprint view or report and locate the sprint there. Check issue history and the sprint field before moving remaining work into a new sprint.
Issues appear in the wrong sprint
Problem: An issue might already have been assigned to another sprint or moved by a teammate after closure.
Solution: Check the issue’s current sprint assignment and status before adding it again. Confirm the destination sprint on the correct board.
Reports seem inconsistent after closure
Problem: The completed sprint’s report reflects its state at closure, while later issue changes can make the current board look different.
Solution: Keep the original sprint intact where possible. Record why work moved and review issue history when a report needs additional context.
An administrator is unavailable
Problem: The sprint was closed accidentally, but no administrator is immediately available to assess a technical correction.
Solution: Avoid unverified changes. Create a replacement sprint if the team needs to keep working, add a note explaining the situation, and ask an administrator to review the original sprint later.
Frequently asked questions
Can you reopen a closed sprint in Jira?
Jira’s standard board interface generally does not provide a button to reopen a completed sprint. If the sprint closed by mistake, ask your Jira administrator to check the options supported by your Jira version and configuration. If restoring its active state is not supported, create a new sprint and move unfinished issues into it. Keep the old sprint’s history intact and explain the change to your team.
What happens to unfinished issues when a sprint closes?
Unfinished issues remain in Jira, but they are no longer part of an active sprint simply because the sprint closed. The team can leave them in the backlog or move them into a later sprint. Before moving an issue, check its current status and sprint assignment. Add a note about carryover so teammates understand why the work appears in a different sprint.
Will creating a new sprint change the old sprint report?
Creating a new sprint and moving unfinished issues usually preserves the old sprint as a completed timebox. The new sprint then reflects the work selected for the next cycle. Reports can still require context if the original sprint closed accidentally or issues changed after closure. Keep a brief explanation of what happened, and ask your Jira administrator to investigate if the report appears incorrect.
Can I change a sprint’s status through the Jira API?
Technical options depend on Jira’s version, permissions, and configuration. Don’t assume that a request to change sprint status will work safely or count as a supported way to restore a completed sprint. Ask your administrator to review current Jira guidance and your organization’s setup before using an API or script. For routine carryover, a new sprint is often easier to understand.
Should I move every unfinished issue into the next sprint?
No. Review each issue with the team before carrying it forward. Some work may no longer be important, may need refinement, or may belong in the backlog rather than the next sprint. For example, an unfinished feature might depend on a decision that has not been made. Move only the work the team has agreed to schedule, and preserve the remaining items for later planning.
Conclusion
When a Jira sprint is closed, first confirm its status and review the unfinished issues. Jira generally does not offer a standard reopen control, so a new sprint is often the clearest way to continue the work.
If the closure was accidental, pause before attempting technical changes and involve your Jira administrator. Preserve the original sprint history, move only the work the team agrees to carry forward, and explain the change.
That approach turns a stressful mistake into a manageable planning adjustment. With a brief closure check and clear sprint ownership, your team can keep work moving without making its history harder to understand.