The Sprint Report shows the list of issues in each sprint. It is useful for your Sprint Retrospective meeting, and also for mid-sprint progress checks. If you have Confluence linked to your JIRA instance, you can also create and/or link Confluence pages to your sprint report. For example, you may want to create retrospective notes for the sprint.

Viewing the Sprint Report

To view the Sprint Report:

Click Reports.

Select Sprint Report from theReportsdropdown at the top of the page.

Select the relevant sprint from the sprint dropdown ('99 Sprint Balloons' in the screenshot below).

The Sprint Report is board-specific, that is, it will only include issues which match your board's Saved Filter.

The values for each issue's Estimate are recorded at the time the sprint is started. Changing the Estimate value afterwards will not be reflected in the Sprint Report. If an issue was added after the sprint was started, then the estimate is recorded at the time it was added to the sprint.

Issues added after the sprint starts are indicated with an asterisk.

The mapping of statuses to your board determines when an issue is considered "To Do" or "Done". See Configuring Columns for more information.

For some issues, the Story Points are not shown in the Sprint Report. This is because the Sprint Report shows information initially included in the sprint – that is, what the team actually committed to. (That being said, if you add an issue with zero story points to a sprint, start the sprint and then change the Story Points, you will see the initial value in the Sprint Report.) If you would like to see all changes, switch to theBurndown Chart instead.

16 Comments

The feature "link to confluence page" on the sprint report used to work well. However, after several updates, it is not possible to create or to link sprint reports to confluence pages anymore. I am admin both in JIRA and Confluence.

Each time, I have "No confluence server configured" error message, as explained here:

I am using JIRA 6.1.7, Agile 6.3.11.0 and confluence 5.4.2, all behind an NGinx server using SSL. Everything is configured correctly so far, and application links is configured with "trusted applications".

I am happy to announce that I solved the issue, after I saw these warnings in the logs of Bamboo:

which points out an issue with the self-signed SSL certificate. Apparently, this occurs when the URL of the webserver is not the same as the CN of the certificate.I reissued a new certificate with the "Common Name" is my.server.url, pushed it into the keystore, and restarted the services.

Now everything works fine again. However, it would be nice to have proper warnings in the log files, it would have saved me a lot of time!

I'm relatively new to JIRA, so this might be a stupid question, but here goes:

In our sprint report all issues are put under "Issues Removed from Sprint" and their statuses are showed as "Open", "In progress", "Ready for test" etc., even though they are all resolved in this sprint. Furthermore the diagram just shows a horizontal line with the value 0, probably meaning that we didn't resolve any issues - even though this is not true.

(I wanted to attach a screenshot to show this, but seems like I don't have permission to do so).

I'm not quite sure what is going wrong for you. You may have your columns configured incorrectly — for an issue to be considered "complete" it has to be in a status that is mapped to the rightmost "Done" column (see Configuring Columns). I'd suggest raising a support request, if this doesn't help.

I think that maybe what went wrong was that we did not have a "Resolved"-column in our Work-board (our rightmost column was a yellow "Ready for prod test"-column). Because of this I have added a new green column, where I've added all the "Resolved"-statuses to. But now I face a new problem:

Instead of just showing the issues we have set as "resolved" in this sprint, it shows a lot of older issues which have nothing to do with this sprint. And we of course only want to see the issues from this sprint; seeing old issues on the work-board is just confusing.

Thanks for your help. I think I've found the solution. We had a "Resolved"-status in between "Closed" and "Ready for prod test" which apparently didn't resolve the issue, but was a kind of limbo-status where the issues were neither in progress or closed and was the reason that fixed issues automatically were transferred to the next sprint instead of being closed. I have now removed this status, and things seems to look as they should now.