Viewing Past Sprints in Jira: A Step-by-Step Process Guide
Can’t find a finished sprint? Learn how to see past sprints in Jira using reports or the backlog to review completed work. Click to discover the steps.
You can find completed sprints in Jira through a Scrum board’s reports or its backlog. The Sprint Report is usually the quickest route to past sprint details, while the backlog can help you browse completed sprints and their issues.
It gets frustrating when a finished sprint seems to disappear, especially when you need to check what the team completed or investigate a change in scope. Board permissions, Jira layouts, and project type can also make the right page harder to spot.
But here's the truth: past sprint information is usually still available if you know where to look. Follow the steps below to locate a completed sprint, inspect its results, and troubleshoot common access problems.
How to See Past Sprints in Jira
Start with the board that ran the sprint. In most Jira Scrum projects, you can open a completed sprint from the board’s reports or backlog.
- Open the Scrum board. Go to the project that managed the sprint, then open its board. If you have several boards, confirm you selected the one used by the team.
- Open the board reports. Select Reports in the project or board navigation. Choose Sprint Report to review a completed sprint’s results.
- Select the sprint. Use the sprint selector near the top of the report. Choose the sprint you want to inspect; completed sprints are listed separately from the active sprint.
- Review the report. Check which issues were completed, which remained unfinished, and whether scope changed during the sprint. The report can also show sprint progress and the final issue status.
- Try the backlog if needed. Open the board’s backlog and look below the current backlog items for the completed sprints section. Expand a sprint to view its issues, if your Jira layout provides that section.
Jira labels and navigation can vary between Cloud and self-managed installations. If the menu names differ, look for the board’s reports or backlog rather than relying on a specific sidebar layout.

What You Can Learn from a Completed Sprint
A past sprint view helps you answer practical questions: Which work reached completion? What carried over? Did the team add or remove issues after the sprint began?
In the Sprint Report, completed and incomplete issues are separated so you can see the final outcome. Scope changes can also help explain why the sprint ended differently from its original plan.
For example, a team may have planned six issues and completed four. If two issues were added midway, the report gives you useful context before you compare the outcome with the original commitment.
Choose Between the Sprint Report and Backlog
Use the Sprint Report when you need a concise review of one sprint’s progress and outcome. It is a good fit for a retrospective or a question about unfinished work.
The backlog is useful when you want to browse several completed sprints or open their individual issues. Think of the report as a sprint summary and the backlog as a place to navigate the board’s work.
Here's why: those views serve different purposes. If you need a sprint-level explanation, start with the report. If you need to open a particular issue or scan several sprint groups, check the backlog.

Review Sprint Changes with Care
A sprint report can show what changed, but the reasons behind a change may require more context. Check issue activity, comments, and team notes before drawing conclusions about a missed commitment.
For instance, an issue could remain incomplete because its acceptance criteria changed, a dependency was delayed, or the team reprioritized urgent work. The report helps you locate the issue; its history can clarify what happened.
The best part? You can use past sprint information to improve planning without treating one sprint as a performance score. Look for recurring blockers and useful adjustments, then discuss them with the team.
Troubleshoot Missing Sprint History
If the sprint does not appear, first confirm that you opened the correct board. A project can have multiple boards, and each board may display a different set of issues and sprint history.
Next, check your access. Your account may need permission to view the project or board, and some report or backlog options may depend on board configuration. Ask a Jira administrator to review access if the relevant pages are unavailable.
You might be wondering: what if the sprint exists, but its issues look incomplete? Check whether the board’s filter includes those issues and whether the team closed the sprint on the expected board.
Past Sprint Tracking with ONES.com
ONES.com is a unified platform for project management and knowledge management, powered by ONES Assistant. ONES Project handles project management and can serve as a Jira alternative for teams that want sprint management and reporting in one project environment.

Teams can use sprint views and built-in reporting to review completed work, while custom workflows and fields help keep project practices aligned with their needs. ONES Project and ONES Wiki are sold separately.
Core Capabilities
- Jira workflow familiarity → Jira-compatible workflows → teams can adapt familiar ways of handling work while moving to a different project management platform.
- Scattered sprint visibility → built-in reporting → teams can review project progress without relying on a collection of separate reporting add-ons.
- Rigid issue processes → custom workflows and fields → teams can represent their own work stages and capture relevant issue details.
- Unclear iteration planning → sprint management → teams can organize work into sprints and review what was completed.
- Repeated manual actions → automation → teams can reduce recurring steps in their project workflow.
- Plugin-heavy setup → native capabilities → teams can reduce reliance on plugins for supported project management needs.
- Separate project and knowledge needs → ONES.com platform → teams can use project management and knowledge management within one platform, choosing ONES Project and ONES Wiki separately.
- Deployment constraints → four deployment options → teams can choose Cloud, On-Premise, Private Cloud, or Air-gapped deployment.
Application Scenarios
A software team reviewing a completed sprint can use sprint management and built-in reporting to discuss finished work, incomplete issues, and process changes. Custom fields can help the team capture details that matter to its planning routine.
An organization with strict infrastructure requirements can evaluate an On-Premise, Private Cloud, or Air-gapped deployment. ONES.com offers full feature parity between its cloud and self-hosted versions, and its free plan supports up to 30 seats.
Common Challenges When Looking Up Old Sprints
- The report is missing. Confirm you opened the correct Scrum board and have permission to view it. Ask a board administrator to check configuration if the report remains unavailable.
- The sprint selector does not show the sprint. Verify that the sprint was completed on this board. A sprint from another board will not necessarily appear in the current board’s report.
- Some issues are missing. Check the board filter and issue access. A board’s scope may exclude issues even when you know they were part of the team’s work.
- The outcome is confusing. Review issue activity and team notes alongside the Sprint Report. This can distinguish a scope change from a blocked or unfinished issue.
Frequently Asked Questions
Where do I find completed sprints in Jira?
Open the Scrum board used for the sprint, then go to Reports and choose Sprint Report. Select the completed sprint from the report’s sprint selector. Depending on your Jira layout, you may also find completed sprints below the items in the board backlog.
Can I view old sprints from the Jira backlog?
Often, yes. Open the correct Scrum board’s backlog and look for a completed sprints section below the current backlog items. Expand a sprint to browse its issues when the section is available. Jira layouts and board settings can affect where that section appears, so use the Sprint Report if you cannot find it.
Why can’t I see a past sprint in Jira?
You may be looking at a different board, lack the required project or board access, or have a board filter that excludes relevant issues. Check the board that ran the sprint first. If the sprint is still missing, ask a Jira administrator to review your permissions and board configuration.
What does the Jira Sprint Report show?
The Sprint Report helps you review a selected sprint’s completed and incomplete issues, progress, and scope changes. It gives you a useful summary of the sprint outcome. To understand why an issue changed or remained unfinished, open its activity and discuss the team’s context.
Conclusion
To see past sprints in Jira, open the Scrum board that ran them and check its Sprint Report or backlog. Use the report to review outcomes and scope changes, then inspect individual issues when you need more context.
If sprint history seems to be missing, confirm the board, check your access, and review its filter or configuration. A clear process makes it easier to learn from finished work and plan the next sprint with better context.