Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

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

 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 from the drop-down at left.
  3. Select the relevant sprint from the sprint dropdown ('99 Sprint Balloons' in the screenshot below).

Related pages:

Screenshot: Sprint Report (click to enlarge)

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.

35 Comments

  1. Michael Walker

    Does this apply to sprint rapid boards, kanban rapid boards, or both?

    I do not see this report option in either, actually, and I am running greenhopper 5.9. I do have one completed sprint, copmleted via the sprint rapid board. Why isn't this showing up?

     

    1. Nicholas Muldoon [Atlassian]

      Hi Michael,

      Apologies for the confusion. This feature is available via GreenHopper Labs as of GreenHopper 5.9.3. 

      It is only available for boards created using the Scrum preset.

      Thanks Michael.

      Regards,
      Nicholas Muldoon 

      1. Michael Walker

        Thanks. I'm told that our onDemand instance is not yet running 5.9.3, but will be updated to it this Sunday. Looking forward to test-driving this feature next week.

         

  2. user-970d9

    Hi there,

    We are using (and loving) this feature. However, we appear to have a range of issues listed in 'removed from Sprint.' We didn't remove them, and editing the issue still indicates the sprint value for that Jira is assigned to the active sprint.

    Is this a bug? Or is there a workflow we're unaware of?

    Thanks

    1. Anonymous

      Have you heard or found any reply to this?   We have the same issue.

      1. Rosie Jameson [Atlassian]

        Can you please check that all your statuses are mapped to columns?

        If this doesn't help, please raise a support ticket at http://support.atlassian.com

  3. lvz

    Will this report be available without using the Scrum preset?

  4. Aldo Cauchi Savona

    Hi, Is there a way to print the burndown charts?

    BTW, love the way Scrum has been implemented. Been using JIRA for 2yrs now and this is what we were waiting for for a long time (smile)

    Thanks,

  5. Tanny

    Hi there,

    What would be the implication if I complete the sprint (actually marking the sprint as completed) before the estimated time?

  6. Tanny

    Hi there,

    I have a couple of questions..

    1) I found out how to remove a parent issue from the current sprint but How would i remove a sub-task from the current sprint?

    2) Once I start a sprint, how do I add issues(New feature or Story) to the current sprint?

    Rgds,

    Tanveer

    1. Rosie Jameson [Atlassian]

      Hi Tanveer,

      1) I found out how to remove a parent issue from the current sprint but How would i remove a sub-task from the current sprint?

      Sorry, you cannot remove a sub-task from a sprint, as sub-tasks always belong to the same sprint as their parent.

      2) Once I start a sprint, how do I add issues(New feature or Story) to the current sprint?

      Please see Adding an Issue to a Sprint

      Thank you,
      Rosie

       

       

       

       

  7. Anonymous

    Wouldnt it be cool if your filters could be used here.

     

  8. RenjithA

    Need to update the image to include the burn-up line as well. Also an additional image to include the report based on time estimates.

  9. Anonymous

    Please can you show the sub-tasks finished on this report too? It is annoying that sub-tasks are completed in a Sprint but there is no evidence of this in the report.

    1. RenjithA

      The idea of Sprint Report is to show the list of stories completed in the Sprint. And stories gets done only when all sub-tasks are completed. The Sprint Report is more from a product/feature point of view (in the from of user stories), rather than the individual technical tasks required to complete the story.

  10. Anonymous

    How can I view completed sprints in versions prior to 5.9?

    1. RenjithA

      If you mean Sprint Report, I guess an upgrade to the latest version of GreenHopper is the only way.

  11. Laszlo Kremer

    I think the Sprint Report should show the re-estimated Story Point values too. During the retrospective meeting the story points may be re-estimated. The current Story Point coulmn could be renamed to Original Story Points and next to it could be the Story Points column showing the story point values of the sprint closing.

    1. Anonymous

      Doing re-estimates for story points is not a good idea. The mistakes in estimation should be applied in the next planning and the team will eventually come closer to realistic figures. After all it is a 'guesstimate' and a moving average across three sprints can be taken as the average velocity for doing a release planning.

      1. Laszlo Kremer

        I think you misunderstood me. The re-estimations are not done during the sprint. It is done during the retrospective meeting, after the sprint, but before the next planning. Having this information on the Sprint Report would be very useful during the next sprint's estimation meeting.

         

         

        1. Anonymous

          Ah, that makes sense. But isn't the retrospective about general ideas on improving things, rather than capturing estimates for each of the items? Capturing of retrospective minutes (at least my experience) was best done in a Confluence page (simple and collaborative) rather than in JIRA.

          1. Laszlo Kremer

            Maybe we are spoiling retrospective meetings' minutes by doing some re-estimations(it is usually held right next to the sprint closing meeting), but the main point is that having this information on the Sprint report would be very useful.

  12. Eric Turley

    I would like to configure the columns(fields) which are shown on our Sprint Report page.

    In fact, I'd like to make a custom field appear.

    Is there a way to customize the Sprint Report page?

    1. Anonymous

      While there is no way to add columns to Sprint reports, I would suggest that Atlassian Answers is the best place for such questions.

  13. Anonymous

    Is there a way to add a sprint summary in the sprint report for future references?

  14. Randy Ollenburger

    Is there a way to get the sprint ID so that I can create my own filters against the sprint?  In V5.9, the sprint report when viewed in the issue navigator revealed the sprint ID. 

    1. RenjithA

      Use the latest version of GreenHopper and you can select the right sprint in Advanced Searching (a drop down will appear with the sprint name)

      1. Randy Ollenburger

        Thanks for the update.  That is what I now found in the documentation.  However, we are not on the latest version.   I did find that by looking at the html source of an issue in the sprint, the ID is exposed. 

  15. Joe O'Reilly

    Is there any chance we are going to be able to generate the notes in the same format as on the "classic" boards, where they are sorted by status? We just prefer that format to this "all in one" list format?

    1. Rosie Jameson [Atlassian]

      You may like to log a request for this at https://jira.atlassian.com/browse/GHS

  16. Peter John Manuel

    How does one actually print this report. 

    Currently Its a manual process of us using the Snipping tool and then pasting the screenshots together..

    1. Rosie Jameson [Atlassian]

      You may like to watch/vote/comment on GHS-6035 - Getting issue details... STATUS

  17. Michael Bennette

    This sprint report is very useful! Especially when looking at it during a retrospective to see what happens in the sprint.

    I do propose that we count the points for the stories added after the sprint started, to the number of complete story points.  I find that the tool is too restrictive when the tool won't count the number of points completed if a story was added after. There are multiple requests added for this. If you agree with this, please vote on GHS-8776 - Getting issue details... STATUS .

    Restricting this does not take into account two scenarios:

    1) team finishes their original commitment and pulls in a story
    2) a change in priority by the product owner and a story is dropped and another story is added. The points of the story dropped won't count in the completed, nor would the story added count.

    The points would basically disappear from the team's velocity. Although I agree of the reasons why such as not changing points after the sprint start or adding stories after the sprint start, I don't think the tool should dictate this.

    Just my two cents to add a little flexibility to an awesome report.

  18. Ed Costello

    Why does the number of closed story points in Report/Sprint Report view differ from the number of closed story points in Plan view for the same filter?  

     

    1. Rosie Jameson [Atlassian]

      I was going to suggest that you watch/vote/comment on GHS-8776 - Getting issue details... STATUS  — but I see that you already have. Many thanks.



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.