How to Reopen a Closed Sprint in Jira: Step-by-Step Guide
Need to fix a closed sprint? Learn how to reopen a closed sprint in Jira using the REST API and explore safer alternatives. Read now.
A sprint can close before you notice unfinished work, a reporting mistake, or an issue that was moved to the wrong place. Then the sprint disappears from your active board, and the usual controls no longer behave as expected. That can make a simple correction feel risky, especially when your team needs an accurate record of what happened.
But here's the truth: Jira does not offer a standard board button to reopen a closed sprint. You may be able to change its state through Jira’s Agile REST API, depending on your Jira setup and permissions. If that option is unavailable or too risky, you can move unfinished issues into a new sprint. This guide walks you through both routes, explains what to check first, and helps you choose the safest way to restore a useful workflow.
How to Reopen a Closed Sprint in Jira
The direct route is to update the sprint’s state to active through Jira’s Agile REST API. Jira’s standard interface does not provide a reopen control for a closed sprint, so use the API only after checking your permissions and team process.
- Confirm the sprint is actually closed. Open your Scrum board and select Reports, then Sprint Report. Choose the sprint in question and check its status and completion details.
- Find the sprint ID. Open the sprint report and inspect the browser address for a sprint identifier, or retrieve sprint details through Jira’s Agile REST API. Make sure the ID belongs to the correct board and sprint.
- Check access and approval. You need permission to manage the sprint and authenticate to the API. Ask your Jira administrator before changing sprint state, especially if the sprint belongs to a shared or regulated project.
- Send the state update. Use a REST client or an approved API tool to make a
PUT request to /rest/agile/1.0/sprint/{sprintId}. Replace {sprintId} with the correct ID and send this JSON body:
{
"state": "active"
}
For Jira Cloud, the full address follows the pattern https://your-domain.atlassian.net/rest/agile/1.0/sprint/{sprintId}. Use your organization’s approved authentication method.
- Verify the result in Jira. Refresh the board and sprint report. Check that the sprint is active, the intended issues appear, and dates and ownership still make sense.
- Stop if Jira rejects the update. Your Jira version, permissions, or sprint conditions may prevent the transition. Don’t repeatedly retry or make unrelated changes. Use the recovery approach below, or ask your administrator to review the response.
Here's why: reopening changes the sprint’s state, which can affect active board views and team reporting. Confirm the result before asking the team to resume work in that sprint.

What Changes When a Sprint Is Closed
Closing a sprint ends its active work period in Jira. Jira records the sprint as complete, and the board moves unfinished work according to the team’s completion choices. Those issues may appear in the backlog or in a later sprint.
For example, imagine a team closes a two-week sprint with three incomplete issues. One issue may have been carried into the next sprint, while another sits in the backlog. If the old sprint becomes active again, confirm where those issues belong before work resumes.
Let me explain: reopening the sprint does not automatically correct every planning decision made at closure. Check issue membership, sprint dates, and status history so your board reflects the team’s actual plan.
When You Can’t Reopen It in Jira’s Interface
Jira’s board interface does not normally include a control for reopening a completed sprint. If you cannot use the API, the straightforward recovery is to continue the unfinished work in a new sprint or return it to the backlog.
For instance, if a closed sprint contains two unfinished tasks and the team has already started a new sprint, add those tasks to the current sprint only after confirming capacity. If the next sprint is not planned yet, leave them in the backlog and prioritize them during planning.
The best part? This approach keeps the team moving without trying to alter a completed sprint’s history. It may not restore the old sprint state, but it gives the team a clear place to continue work.
Use the API Carefully
An API state change can be useful when a sprint was closed by mistake and your Jira setup accepts the update. However, an accepted request does not guarantee that reopening is the right choice for your project’s reporting or audit practices.
Before making the request, record the sprint name, its dates, and the issues you expect to see. Keep the change limited to the sprint state. Avoid changing issue status or dates at the same time, since that makes it harder to identify what caused an unexpected result.
You might be wondering: what if the API returns an error? Read the response, confirm the sprint ID and permission level, then contact your Jira administrator. If your organization does not permit state changes through the API, use the backlog or a new sprint instead.
Verify the Board and Reports After Recovery
After reopening a sprint or moving its issues, check the board and reporting views together. Confirm that each issue has the expected sprint assignment, status, and owner. Compare the sprint’s displayed dates with the schedule your team agreed on.
For example, a task can appear in the right sprint while retaining a status that suggests it is already complete. That mismatch can confuse stand-ups and reports. Ask the issue owner to verify the task’s current state before treating it as active work.
Here's why: a clean board helps everyone understand what the team is doing now. A short review after a sprint correction can prevent duplicate work and misleading progress discussions.
Prevent Accidental Sprint Closure
Make sprint closure a deliberate team action. Before selecting Complete sprint, review unfinished issues and decide whether each belongs in the backlog or a future sprint. A quick check during the final stand-up often catches misplaced work.
You can also agree on who is allowed to close sprints and what the team should do if one closes by mistake. For example, a small team might ask the Scrum Master to verify the sprint report before closure, while a larger team may include the check in its release routine.
Clear ownership reduces rushed corrections. It also gives Jira administrators enough context to assess whether an API change is appropriate.
Jira Sprint Management with ONES.com
ONES.com is a unified project management and knowledge management platform powered by ONES Assistant. ONES Project is its project management product and a Jira alternative; ONES Wiki is its knowledge management product and a Confluence alternative. They are sold separately.

When sprint recovery exposes gaps in your workflow, ONES Project gives teams another way to manage agile planning. It supports Jira-compatible workflows, sprint management, custom fields, automation, and built-in reporting. Teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment, with feature parity between cloud and self-hosted versions.
Core Capabilities
- Pain: A sprint mistake leaves the team unsure where unfinished work belongs. ONES capability: Sprint management supports planning and issue organization. Result: The team can place remaining work into a clear sprint plan.
- Pain: A team relies on a Jira-compatible process and fears disrupting familiar routines. ONES capability: Jira-compatible workflows support familiar ways of handling issues. Result: Teams can preserve established process patterns while evaluating a Jira alternative.
- Pain: Default issue fields do not capture the details a team needs during planning. ONES capability: Custom fields let teams track relevant information. Result: Sprint decisions can reflect the project’s specific requirements.
- Pain: Workflow changes require repeated manual updates. ONES capability: Custom workflows and automation support defined process steps. Result: Routine transitions can follow consistent team rules.
- Pain: Teams have to rely on add-ons for common project insights. ONES capability: Built-in reporting provides project and sprint views. Result: Teams can review progress with fewer extra plugins.
- Pain: A cloud-only deployment does not fit a company’s environment. ONES capability: Deployment options include Cloud, On-Premise, Private Cloud, and Air-gapped. Result: Organizations can choose an operating model that fits their constraints.
- Pain: A project team wants to manage sprints and knowledge in one ecosystem. ONES capability: ONES.com combines project and knowledge management, with ONES Project and ONES Wiki available separately. Result: Teams can select the products that match their needs.
- Pain: A team wants to test a project platform before a wider rollout. ONES capability: The free plan supports up to 30 seats. Result: A team can evaluate its project workflow with a limited group.
Application Scenarios
A software team closes a sprint before reviewing all unfinished issues. It can use ONES Project’s sprint management and reporting to organize the next planning cycle, while custom workflows help define how incomplete work moves forward.
An organization with restricted network requirements needs project management without a cloud deployment. It can consider ONES Project’s On-Premise, Private Cloud, or Air-gapped deployment options and assess the workflow against its own operational needs.
Common Challenges and Practical Solutions
- The sprint ID is unclear. Confirm the ID in the sprint report or retrieve sprint details through the Agile REST API. Verify the sprint name before sending any update.
- The API rejects the state change. Check the response and ask an administrator to review permissions and Jira configuration. If reopening is unsupported in your setup, move remaining work to a new sprint or the backlog.
- Issues appear in the wrong sprint afterward. Review each issue’s sprint assignment and coordinate with its owner. Correct assignments one at a time so the team can follow the changes.
- Reports no longer match team expectations. Compare the sprint report, issue statuses, and agreed dates. Explain the correction to the team so everyone understands how to interpret the updated board.
FAQs
Can I reopen a closed sprint from the Jira board?
Jira’s standard board interface does not normally provide a button to reopen a completed sprint. Depending on your Jira version, setup, and permissions, an administrator may be able to change the sprint state through the Agile REST API. If that route is unavailable, move unfinished issues to a new sprint or back to the backlog.
What API request can change a closed sprint to active?
The Agile REST API sprint update endpoint is PUT /rest/agile/1.0/sprint/{sprintId}. The request body uses {"state":"active"}. Replace the sprint ID with the correct value and use your organization’s approved authentication method. Confirm the request is permitted in your Jira environment before making the change.
Will reopening a sprint restore every issue automatically?
No. Check the sprint’s issue assignments after changing its state. Issues may have been moved to the backlog or another sprint when the original sprint closed. Verify each issue’s current sprint, status, and owner so the team does not assume the old plan was restored completely.
What should I do if Jira will not reopen the sprint?
Ask your Jira administrator to check the API response, permissions, and project configuration. If the change is not supported or approved, put unfinished issues in the backlog or a new sprint. Choose the destination with the team, then confirm issue status and ownership before continuing work.
Conclusion
A closed Jira sprint usually cannot be reopened through the board interface. If your Jira setup permits it, an administrator or authorized team member can try the Agile REST API state update and verify the result carefully.
If reopening is unavailable, move unfinished issues into a new sprint or the backlog and make the next plan explicit. Check issue assignments and reports after any correction. A deliberate closure routine can also prevent the same disruption from happening again.