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 version 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 Version Report shows your team's progress towards the completion of a version. The Version Report also shows you the predicted Release Date, based on your team's average rate of progress (velocity) since the start of the version, and the estimated amount of work remaining.
Before you begin
This page only applies to Scrum boards.
Viewing the Version Report
Click Projects in the navigation bar and select the relevant project
Click Reports, then select Version Report
Select the relevant version from the Version Report drop-down
Understanding the Version Report
Before you start using the Version Report, you should get to know how it works. The following information will help you understand the key functionalities of the Version Report:
The Version Report is board-specific – that is, it will only include issues that match your board's saved filter.
The Version Report will exclude issues of a 'sub-task type'.
The Version Report shows 'Released' versions but not 'Archived' versions. For more about version status, see Managing versions (Jira admin documentation).
The Version Report is based on your board's column mapping. 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 horizontal axis starts on the version's Start Date; or if no Start Date is specified, the date on which an issue was first added to the version. The graph shows the state your version was in at any given point in time, in terms of your total and completed Story Points (or other Estimation Statistic of your choice), so that you can see how the scope may have changed, and how you are progressing towards completion of the estimated work.
The graph shows you the following predictions:
the Predicted Release Date (blue line) – that is, the date at which you can expect all issues in your version to be complete, based on your average daily velocity and the amount of estimated work remaining.
the Predicted Release Date (Optimistic) (shaded area to the left of the blue line) – that is, the earliest date by which you might expect the version to be complete. (The 'optimistic' date is calculated by adding 10% to the average daily velocity.)
the Predicted Release Date (Pessimistic) (shaded area to the right of the blue line) – that is, the latest date by which you might expect the version to be complete. (The 'pessimistic' date is calculated by subtracting 10% from the average daily velocity.)
10% of the estimated work for the version will need to be complete before the predictions can be calculated.
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?