How to View Previous Sprints in Jira: A Step-by-Step Guide
Can't find a finished sprint? Learn how to see previous sprints in Jira with Sprint Reports and backlog views. Read now to review past work fast.
You finished a sprint last week, and now you need to check which issues were completed. But the old sprint seems to have vanished from your Jira board. Maybe you need to confirm a commitment, investigate a missed deadline, or explain why the sprint’s scope changed.
It’s frustrating when you know the work happened but can’t quickly find the right view. Clicking through the backlog without knowing where completed sprints live can waste time, especially when your team has run many sprints.
Here’s the truth: you can usually review a past sprint through the board’s Sprint Report or its completed-sprints section. The steps depend on your board type and Jira layout, so I’ll show you both routes, explain what you can learn from each, and cover common access issues.
How to View Previous Sprints in Jira
For a Scrum board, open the board, choose Reports, select Sprint Report, and pick the completed sprint from the sprint selector. To see completed sprint lists, open the board’s backlog and look for the completed-sprints section.
Jira menus can differ slightly across versions and configurations. Start with the report if you need a detailed sprint review; use the backlog when you just need to locate completed work.
Open the correct Jira project and board. Navigate to the project where the sprint was run, then open the Scrum board your team used. If you have multiple boards, check the board name and project before continuing.
Open the board’s reports. Find Reports in the board navigation and choose Sprint Report. If you can’t find that option, confirm that you’re on a Scrum board. Reports and menu locations can vary by Jira version.
Select the sprint you want to review. Use the sprint selector near the top of the report. Choose a completed sprint by its name or dates. If the list is long, compare the sprint dates with the period you’re investigating.
Review the sprint’s results. Look at the issues completed, work left incomplete, and any scope changes shown in the report. The available details can depend on your board settings and estimation method.
Try the backlog if you only need the completed sprint list. Open the board backlog and scroll to the completed-sprints section. Expand it if it’s collapsed, then choose a sprint to inspect its issues.
Check access and board settings if the sprint is missing. Make sure you’re viewing the board that ran the sprint and that you have permission to view its issues. A board’s filter may also limit which work appears.
Quick example: If you need to check whether a bug made it into last month’s sprint, open the team’s Scrum board, choose Sprint Report, and select the sprint by date. If you only need to find the sprint name, the backlog’s completed section may be faster.

What You Can Learn from a Past Sprint
A completed sprint report helps you understand both the outcome and the path the team took. You can review completed issues, unfinished work, and changes made after the sprint began. That makes the report useful for sprint reviews, retrospectives, and follow-up planning.
For example, suppose your team planned 20 issues but completed 16. The four remaining issues show what carried forward, while changes in sprint scope can help explain why the plan shifted. Use that context before drawing conclusions about the team’s delivery.
Here's why: a sprint result is more informative when you compare the original plan with what changed during the sprint. If an issue was added halfway through, the final count alone won’t explain the extra work.
Find Completed Sprints in the Jira Backlog
The backlog is a convenient place to browse completed sprints and their issues. Open the board backlog and look below the active sprint or future work for a completed-sprints section. Depending on the interface, you may need to expand the section to see its sprint list.
Use this route when you want to locate an older sprint quickly or inspect its work without starting with a report. For instance, a project lead can open a completed sprint and scan its issue names to find a particular task.
But here's the catch: the backlog shows work associated with the board you opened. If a sprint or issue seems absent, verify that you’re looking at the right board and that its filter includes the project and issues you expect.

Why a Previous Sprint May Not Appear
A missing sprint doesn’t always mean Jira has removed it. You might have opened a different board, chosen a Kanban board instead of a Scrum board, or landed in a project with a similar name. Check the board before changing settings.
Board filters can affect what you see. For example, a filter that includes only one project may exclude issues from another project, even if your team remembers working on them in the same sprint. Ask a board administrator to review the filter if the sprint looks incomplete.
Permission settings matter, too. If you can open the board but can’t view certain issues, the report may not show the full picture. Let me explain: ask a Jira administrator or project administrator to confirm your project access and board permissions.
Use Past Sprint Details for Better Planning
Review a past sprint with a specific question in mind. You might ask what remained unfinished, when work was added, or whether an issue moved into a later sprint. A focused review makes it easier to turn history into a practical planning improvement.
For example, if several large issues repeatedly carry over, discuss whether the team is splitting work into small enough tasks. If new work often appears mid-sprint, clarify how urgent requests should be assessed before they affect the plan.
The best part? A past sprint can support a useful conversation without becoming a performance scorecard. Compare plans and outcomes, note relevant changes, and agree on one adjustment the team can test in its next sprint.
ONES.com Solution for Sprint and Project Context

Value Proposition
ONES.com brings project management and knowledge management together in a unified platform. ONES Project supports sprint and project workflows as a Jira alternative, while ONES Wiki provides a knowledge base as a Confluence alternative; each is sold separately.
If your team wants sprint planning, reporting, and project knowledge in a coordinated environment, ONES.com offers a practical option to evaluate. The right fit depends on your team’s workflows, hosting needs, and collaboration habits.
Core Capabilities
Fragmented sprint work → Jira-compatible workflows in ONES Project → Teams can work with familiar issue and sprint patterns while evaluating a Jira alternative.
Limited visibility into progress → Built-in reporting → Teams can review project and sprint progress without relying on a patchwork of reporting add-ons.
Workflows that don’t match team needs → Custom workflows and fields → Teams can adapt issue handling and tracking to their processes.
Sprint planning spread across different steps → Sprint management → Teams can organize sprint work within their project management environment.
Repeated manual actions → Automation → Teams can automate routine workflow steps and reduce repetitive administration.
Too many separate plugins → Broad native capability coverage → Teams can assess whether built-in features reduce the need for extra plugins.
Restrictions on where services run → Four deployment options: Cloud, On-Premise, Private Cloud, and Air-gapped → Organizations can choose an environment that fits their operational requirements.
Concern about feature gaps in self-hosted use → Full feature parity between cloud and self-hosted versions → Teams can consider deployment needs without assuming that self-hosting means giving up features.
Small teams evaluating a new platform → Free plan for up to 30 seats → A team can try the platform with a limited group before considering wider adoption.
Application Scenarios
A team reviewing sprint outcomes: A project team can use ONES Project to manage sprint work and built-in reporting, then discuss unfinished issues and planning changes during its retrospective.
An organization with hosting requirements: A company that needs an on-premise or air-gapped deployment can evaluate those options while considering project management needs. Full feature parity between cloud and self-hosted versions gives the team a consistent feature set to assess.
A team connecting project work with shared knowledge: A team can manage work in ONES Project and keep related knowledge in ONES Wiki. The products are sold separately, so the team can assess each one for its own needs.
Common Challenges When Reviewing Old Sprints
The Sprint Report option isn’t visible
Problem: You can open a board but don’t see a Sprint Report. One likely cause is that you’re viewing a Kanban board, or the interface places reports elsewhere.
Solution: Confirm that the board is a Scrum board, then check its navigation and reporting options. If you still can’t find the report, ask a Jira administrator to confirm your board access and configuration.
The sprint list doesn’t include the sprint you expect
Problem: The sprint selector or backlog doesn’t show the sprint you remember. You may be checking a different board or a board with a filter that excludes related issues.
Solution: Confirm the board name, project, and sprint dates. If the sprint remains missing, ask the board administrator to check the board filter and whether the sprint belongs to that board.
The report appears incomplete
Problem: Some issues you expect to see aren’t visible, or the report doesn’t show the details you need. Access restrictions, board filters, and estimation settings can affect what appears.
Solution: Check whether you can open the individual issues and verify that the board includes them. Ask an administrator to review permissions and reporting configuration if the issue continues.
The team can’t agree on what changed
Problem: Team members remember the sprint differently, making it difficult to understand why work moved or scope changed.
Solution: Use the report and issue history to anchor the discussion in specific work and dates. Focus on what the team can adjust, such as breaking down large issues or agreeing how to handle urgent additions.
FAQs About Viewing Earlier Jira Sprints
Can I view a previous sprint in Jira?
Yes. On a Scrum board, open Reports, choose Sprint Report, and select the completed sprint. You can also open the board backlog and expand its completed-sprints section. The exact menu location may vary with your Jira version and configuration, so check that you’re using the board where the sprint ran.
Why can’t I see completed sprints in the Jira backlog?
First, confirm that you opened the correct Scrum board. Then look near the bottom of the backlog for a completed-sprints section and expand it if needed. If the sprint is still missing, the board filter may exclude relevant issues, or your permissions may limit what you can see. A board administrator can check those settings.
Can I reopen a completed sprint to see its issues?
You can review a completed sprint through its report or the completed-sprints section in the backlog. Viewing its issues is different from reopening it. If you need to change a completed sprint or move work, check your team’s Jira process and permissions first, since available actions depend on your configuration.
What’s the difference between a Sprint Report and the backlog?
A Sprint Report presents a past sprint’s progress and outcome, making it useful for reviewing completed and unfinished work. The backlog offers a way to browse sprint lists and issues associated with a board. Choose the report when you’re assessing what happened; use the backlog when you mainly need to locate work or a sprint.
Conclusion
To view a previous sprint in Jira, open the Scrum board that ran it and select the sprint from its Sprint Report. If you only need to browse completed sprints, check the board backlog’s completed-sprints section.
If something is missing, verify the board, its filter, and your access before assuming the sprint has disappeared. Then use the sprint’s history to discuss concrete improvements, such as clearer work breakdown or a better process for handling new requests.
Finding an old sprint shouldn’t derail your review. With the right board and view, you can trace the work, understand what changed, and carry a more informed plan into the next sprint.