Skip to end of metadata
Go to start of metadata

(info) This page only applies to Scrum boards.

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:

  1. Click Reports
  2. Select Sprint Report from the Reports dropdown at the top of the page.
  3. Select the relevant sprint from the sprint dropdown ('99 Sprint Balloons' in the screenshot below).
Screenshot: Sprint Report (shows linked pages which requires Confluence — see below)

Please note:

  • 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 the Burndown Chart instead.

Linking Confluence pages to the Sprint report

Before you begin, see Using JIRA Agile and Confluence together for prerequisites.

To create a new Confluence page for a Sprint report:

  1. Navigate to the Sprint report, as described above.
  2. Click Linked pages above the report chart.
  3. Click Create page. The 'Create' dialog in Confluence will be displayed, with the Retrospectives blueprint selected (select a different blueprint, if you don't want to use it).

To link an existing Confluence page to a Sprint report:

  1. Navigate to the Sprint report, as described above.
  2. Click Linked pages above the report chart.
  3. Click Link page, search for the page you want and select it.


  1. 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:

    However, in the logs of NGinx, I can see the queries to confluence, as explained in my posts here:

    Of course, I have the project admin permission in JIRA Agile.

    I am using JIRA 6.1.7, Agile 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".

    Maybe I should file a bug?

    1. 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!

  2. How can I view Burndown chart x-axis Days in the sprint, y-Axis hour left to complete

    1. Hi Vinay,

      The report described on this page, the Sprint Report, should do what you are asking. 

      Kind regards,


  3. Hi,

    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).

    How come this happens? I assume we do something wrong somewhere?

    Best regards,

    1. Hi Johannes,

      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. 

      Kind regards,

      1. Hi Andrew,

        Thanks for your reply.

        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.

        Best regards,

        1. Hi Johannes,

          You could try doing a search for issues which have the Sprint field set to the sprint selected for your sprint report. 

          e.g. project = "<your project>" AND issuetype = Story AND Sprint = "<your sprint>"

          If there are any stories incorrectly assigned to the sprint, then you can edit the Sprint field to remove them from the sprint. 

          If that doesn't work, I'd suggest raising a support request. Our support team will be able to help you figure out what's going wrong.

          Kind regards,

          1. Hi Andrew,

            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.

            Thank you.

            Best regards,

  4. Sprint report load times for us are extremely slow.  Upwards of 10-15 seconds.  Is there a way we can quicken the load times or adjust the cache to speed up the average users performance?

  5. certain boards on our prod JIRA instance are timing out:


    Users are getting a red dialog box in JIRA: Error: Request timed out

    1. Hi JBarr and Dowjones Admin,

      Can you raise a support request with our support team? They will be able to help you figure out what is going on.

      Kind regards,

  6. Hi there. Is it possible to customize reports? We'd like to add the business value field to the sprint report, and be able to export the report to PDF / email etc.

    1. Hi Delany,

      Unfortunately, it's not possible to customize or export reports, as you've described. You may like to vote and/or comment on these tickets:

      GHS-7353 - Ability to Customize the JIRA Agile Reports Open

      GHS-6135 - As an agile board user, I would like to export the reports into a common format to show my product owner, who doesn't have access to my JIRA, so that he/she can see the sprint progress. Open

      Kind regards,

      1. I agree that PDF customisable reports are essential. I will be adding my vote

  7. As with Version Reports, the ability to customise this to include sub-tasks must be made available. There's absolutely NO POINT in having sub-tasks at all if you don't let the most basic reporting features use them. Thanks.