Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your existing Jira Software Cloud site to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer next-gen projects.
Create powerful rules to start automating your manual, repetitive processes.
View and understand the sprint report
Are you on the right help page?
The following information only applies to classic projects.
To check which project you need help with, look at the bottom of your project’s left-hand sidebar:
If you see an icon stating You’re in a next-gen project with Give feedback and Learn more menu items, you're in a next-gen project. Check out our next-gen project documentation.
If you don’t, you're in a classic project.
The Sprint Report shows the list of issues in each sprint. It is useful for your Sprint Retrospective meetings, and also for mid-sprint progress checks.
If you have Jira Software connected to Confluence, you can create a 'Retrospectives' page via the Linked pages link. See Linking a Confluence page to a sprint for details.
Before you begin
This page only applies to Scrum boards.
Estimates on sub-tasks are not included in the Sprint Report. (Only estimates on parent issues are included.)
Viewing the Sprint Report
Click Projects in the navigation bar and select the relevant project
Click Reports then select Sprint Report
Select the relevant sprint from the sprint drop-down
Understanding the Sprint Report
Before you start using the Sprint Report, you should get to know how it works. The following information will help you understand the key functionalities of the Sprint Report:
The Sprint Report is board-specific – that is, it will only include issues that match your board's saved filter.
Issues added after the sprint starts are indicated with an asterisk.
An issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your board. Similarly, an issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board. See Configuring columns for more information.
The grey line is a guideline that's drawn from the total estimate of the issues at the start of the sprint, to 0 at the end of the sprint. The grey line stays flat during non-working days.
The red line represents actual work done during the sprint — it's drawn from the total estimate of the issues at the start of the sprint, and it goes higher or lower as your team works on the issues in the sprint. Note that the red line shows the current total estimate for unresolved issues at any point in the sprint. It also reflects issues that are added or removed from the sprint.
If your board is configured to track remaining estimates and time spent, a green line will display in the Sprint Report, indicating work logged on issues.
Need help? If you can't find the answer you need in our documentation, we have other resources available to help you. See Getting help.
Was this helpful?