GreenHopper is now called JIRA Agile. Learn more.

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 the Agile link's down-arrow in the top navigation bar, then select your preferred board from the resulting dropdown menu.

  2. Click Report, then select Sprint Report.
  3. Select the relevant sprint from the sprint dropdown ('99 Sprint Balloons' in the screenshot below).

On this page:


Related pages:

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.
  • Issues added after the sprint starts are indicated with an asterisk.
  • 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.

7 Comments

  1. I'm seeing the error "An error occured when storing a JSON property {0}" when trying to link a page to the sprint report.

    Anybody else having the same problem?


  2. What versions of Jira, Confluence and Agile are needed for this feature?

    1. Hi Jason,

      You will need at least JIRA Agile 6.3.5 and Confluence 5.4 (see this page). JIRA Agile 6.3.5 will work on JIRA 5.2, 6.0 or 6.1 (see this page), although we strongly recommend that you use at least 6.0.

      Kind regards,
      Andrew

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

    https://answers.atlassian.com/questions/263207/linked-pages-between-agile-and-confluence

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

    https://answers.atlassian.com/questions/125007/issue-links-wiki-page-you-do-not-have-permission-to-view-this-page

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

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

    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!