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

(info) This page only applies to Scrum boards.

The Epic Report shows a list of complete, incomplete and unestimated issues in an epic. It is particularly useful for planning work for an epic that may extend over multiple sprints.

Use the Epic Report to understand the progress towards completing an epic over time, and to track the amount of remaining work that's incomplete or unestimated.

To view the Epic 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 Epic Report from the drop-down at left.
  3. Select the relevant epic from the epic dropdown ('Detail View' in the screenshot below).

(tick) Click View in Issue Navigator to jump to the Issue Navigator and see a list of all the epic's issues.

 

Related pages:

 

Screenshot: Epic Report (click to enlarge)

(info) Please note that the graph will look different if you are using Issue Count as your Estimation Statistic (rather than Story Points, as shown in this screenshot).

 

10 Comments

  1. Tom Vercellotti

    Feb 07, 2013

    we are not able to see this Epic report - is it not available in the OnDemand edition?

    1. Rosie Jameson [Atlassian]

      Feb 11, 2013

      Apologies, the Epic Report was released in GreenHopper 6.1.2, which should be deployed to OnDemand within the next fortnight.

  2. David Murgatroyd

    Feb 13, 2013

    As an Epic Report user I want the drop down to put completed Epics are at the bottom so that I spend less time navigating pass them.

  3. Markus Jankowski

    Mar 07, 2013

    If I use 'Original Estimate' I can see e.g. 'Total Original Time Estimate' in the Report. E.g. for an Epic Overview Reporting in a Dashboard I need this value in the Issue Navigator. If I add the column, it is empty. Are there any plans to make these values accessible in the Issue Navigator?

  4. Morgan Belais

    Apr 15, 2013

     

    Do you plan to implement displaying of story sub-tasks ? For us this is kind of mandatory.

    Thanks

  5. Tom Vercellotti

    Apr 15, 2013

     

    I also agree with Morgan above, in that Greenhopper needs to show the hierarchy of epics->stories->tasks->sub tasks in all of the views (including the Epic report).  This is one of the biggest complaints that our teams have with the tool to date.  Even the planning and work tracking board gets very messy when you cannot see the hierarchy.  Any future plans to address this?

  6. Tom Kotecki

    Apr 26, 2013

    Hi Morgan, Tom,

    We do not plan to display subtasks in the planning mode, as during sprint planning the focus really is on stories (i.e. you can't commit to a subset of subtasks for a sprint anyway). You can, however, see them in work mode, and we intend to implement swimlanes by epic soon, which will allow you to see the entire hierarchy (epics -> stories -> subtasks) there.

    Hope this helps

    Tom Kotecki

    1. Tom Vercellotti

      Apr 26, 2013

       

      Thanks for taking the time to respond to this Tom.  Maybe tasks then should be hidden from the planning mode all together if that is the philosophy you want to follow?  It is possible to create in the tool today a "task" issue type associated with an epic.  This can then lead to confusion as well when planning what has to be done.  Overall if the reports, work tracking areas, issue detailed views, etc could display more of the hierarchy that would go a long way to make the information more understandable.

       

      Tom V

      1. Rosie Jameson [Atlassian]

        May 15, 2013

        You may like to watch/vote/comment on these issues:

        GHS-6391 - Getting issue details... STATUS

        GHS-8234 - Getting issue details... STATUS

  7. Pat Pigatti

    Aug 13, 2013

    Hi,

    is there a way to change the sort order of the linked stories completed for an Epic on the Epic Report other than by the ticket create date? Sorting it on the sprint and showing  the sprint would be beneficial. Regards, Pat



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.