How to View Past Sprints in Jira: A Quick Step-by-Step Guide
Need to find an old sprint? Learn how to view past sprints in Jira, check sprint reports, and troubleshoot missing history. Click to discover the steps.
Finding an old Jira sprint can be frustrating when the board only shows current work. You may remember the sprint name, but not where Jira hides its history. Clicking through issues one by one takes time, and it can leave you unsure whether you are seeing the complete sprint.
Here’s the truth: Jira keeps past sprint information in a few places, and the Sprint Report is usually the quickest way to review a completed sprint. I’ll walk you through the steps, explain what you can see, and cover what to check if a sprint seems missing.
How to view past sprints in Jira
For a quick review, open the Scrum board’s reports, choose Sprint Report, and select the completed sprint you want. The report displays sprint details and the issues associated with it.
- Open the right Jira project. Go to the project that contains the Scrum board used to run the sprint.
- Open the board. From the project navigation, select the board used by your team. If the project has several boards, check the board name before continuing.
- Open Reports. Select Reports in the board navigation. Depending on your Jira layout, you may need to open the board menu first.
- Choose Sprint Report. Jira opens a report for a sprint. Use the sprint selector near the top of the page to choose a completed sprint.
- Review the sprint. Check the completed work, issues not completed, and any scope changes shown in the report. Select an issue to open its details.
Here’s why this route works: the Sprint Report is designed to show a sprint’s history, rather than just the issues currently visible on your board. If you cannot find the sprint selector or report, check that you opened the correct Scrum board.

Choose the board that ran the sprint
A past sprint belongs to the board where the team planned and completed it. Opening another board in the same Jira project may show a different sprint list, even when both boards display some of the same issues.
For example, a team might have one board for the whole engineering group and another for a particular product. If you ran the sprint on the engineering board, its history may not appear on the product board.
You might be wondering: how can you tell which board is the right one? Check the board name, project navigation, and team’s usual sprint planning location. If you still are not sure, ask a board administrator or teammate who participated in the sprint.
What the Sprint Report can tell you
The Sprint Report helps you review what happened during a completed sprint. Depending on the Jira setup and report view, you can inspect completed issues, work left unfinished, and changes made after the sprint began.
That context matters during a retrospective. For instance, if a sprint began with 18 issues and later gained several more, the report can help explain why the team finished fewer planned issues than expected.
Let me explain: a sprint report is a record of sprint activity, not a guarantee that every issue tells the full story. Open an issue when you need to check its status, comments, or activity details.
Check past sprints in the backlog
Some Jira Scrum boards also let you review completed sprints in the backlog. Open the board’s backlog view and look for a completed-sprint section, which may be collapsed or positioned below active work.
This can be handy when you want to scan sprint names or get back to recent work quickly. For a fuller review of what changed and what was completed, the Sprint Report is usually more useful.
Jira navigation can vary between layouts and board configurations. If you do not see completed sprints in the backlog, try the report route instead and confirm that your board is Scrum rather than Kanban.

Why a past sprint may not appear
When a sprint seems to be missing, first confirm that you are using the same board the team used to run it. Then check whether the sprint is completed and whether you have access to the board and its issues.
Board filters can also affect which issues appear. A board may show only issues that match its filter, so a past sprint can look incomplete if some associated issues no longer match those conditions.
The best part? These checks are quick. Try the Sprint Report on the correct board, then ask a Jira administrator to review board access or filter settings if the sprint still does not appear.
A project management alternative: ONES.com
Value proposition: ONES.com combines project management and knowledge management in one platform, while ONES Project is its project management product and a Jira alternative. The products are sold separately, so teams can choose the capabilities that fit their needs.

If your team is reviewing Jira sprint history because project tracking feels scattered, a different project management setup may be worth evaluating. ONES Project includes sprint management, reporting, custom workflows, and fields. It also supports Jira-compatible workflows, which can help teams familiar with Jira concepts assess a different environment.
Core capabilities
- Work is spread across different places: ONES.com provides project management and knowledge management in one platform. ONES Project and ONES Wiki are separate products, so you can select the product relevant to your work.
- Sprint progress is difficult to review: ONES Project includes sprint management and built-in reporting. Teams can use those capabilities to track work and review progress.
- Standard workflows do not fit your process: Custom workflows let teams shape how work moves between stages. This can make project tracking more relevant to the team’s actual process.
- Issue fields do not capture needed details: Custom fields can record information specific to a team or project. That gives teams more control over how work is described and organized.
- Routine steps take repeated manual effort: Automation can handle supported recurring actions. Teams can spend less time on repetitive workflow tasks.
- Teams rely on too many add-ons: Native capabilities can reduce the need for plugins for supported project management needs. Fewer add-ons may also mean fewer separate settings to maintain.
- Hosting requirements limit options: ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Teams can evaluate a deployment that fits their environment.
- Self-hosted teams worry about missing features: ONES.com states that its cloud and self-hosted versions have full feature parity. This helps teams compare deployment choices without assuming a feature gap.
Application scenarios
A team replacing Jira: A project team that wants familiar Jira-compatible workflows can evaluate ONES Project as a Jira alternative. It can review sprint management, custom fields, automation, and reporting against its current requirements.
A team with restricted hosting needs: An organization that cannot use a standard cloud deployment can assess On-Premise, Private Cloud, or Air-gapped deployment options. Its team can consider the hosting environment alongside project management needs.
Common challenges when reviewing Jira sprint history
- The sprint is missing from the selector. You may be on the wrong board. Open the board that ran the sprint and check its Sprint Report.
- The report looks incomplete. A board filter may exclude some issues. Ask a board administrator to check the filter and confirm the issues still match its conditions.
- You cannot open the report or an issue. Your Jira permissions may limit access. Ask the project or board administrator to review your permissions.
- You are unsure whether the sprint finished. Check the sprint’s status on the board or ask a teammate who ran it. A sprint that is still active may not appear among completed sprints.
FAQs about viewing old Jira sprints
Where do I find completed sprints in Jira?
Open the Scrum board that ran the sprint, select Reports, and choose Sprint Report. Use the sprint selector to open a completed sprint. Some boards also show completed sprints in the backlog. If you do not see the sprint, confirm that you are on the correct board and have access to it.
Can I view a past sprint from the Jira backlog?
Often, yes. Open the Scrum board’s backlog and look for a completed-sprint section. It may be collapsed or lower on the page. Backlog layouts and board configurations vary, so the completed-sprint list may not be visible in every setup. The Sprint Report is another place to review a completed sprint.
Why can’t I see an old sprint in Jira?
You may be looking at a different board from the one where the sprint ran. Board filters, access permissions, and the sprint’s status can also affect what appears. Start by checking the board name and opening its Sprint Report. If the sprint remains missing, ask a Jira administrator to review access and board settings.
What can I see in a Jira Sprint Report?
A Sprint Report gives you a view of a sprint’s issues and progress. You can review completed work, work left unfinished, and scope changes where Jira displays them. Open individual issues to inspect their details or activity. The report helps with sprint review, though you may need to check issue history for additional context.
Can I view past sprints on a Kanban board?
The Sprint Report is associated with Scrum sprint workflows, so it may not be available on a Kanban board. Kanban boards track ongoing work differently and do not use the same sprint cycle. If your team ran sprints, check the Scrum board used for planning and completion.
Conclusion
To view past sprints in Jira, open the Scrum board that ran the sprint, go to Reports, and select Sprint Report. Choose the completed sprint from the selector, then review its issues and progress.
If the sprint is missing, check the board, filter, permissions, and sprint status before assuming the history is gone. Once you find the right view, you can use it to revisit completed work and bring clearer context to your next retrospective.