Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Create powerful rules to start automating your manual, repetitive processes.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
This page is for company-managed projects
If the lower-left of your project sidebar says you're in a team-managed project, check out these team-managed project articles instead.
Learn more about the difference between company-managed and team-managed projects.
The Epic Report shows a list of complete, incomplete, and unestimated issues in an epic. It is particularly useful in 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.
Before you begin
This page only applies to Scrum boards.
Viewing the Epic Report
Click Projects in the navigation bar and select the relevant project
Click Reports then select Epic Report
Select the relevant epic from the epic drop-down
Click View in Issue Navigator to jump to the Issue Navigator and see a list of all the epic's issues.
Understanding the Epic Report
Before you start using the Epic Report, you should get to know how it works. The following information will help you understand the key functionalities of the Epic Report:
The Epic Report is based on your board's column mapping. An issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your board. Similarly, an issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board. See Configuring columns for more information.
The graph will look different if you are using Issue Count as your Estimation Statistic (rather than Story Points, as shown in the screenshot above).
Need help? If you can't find the answer you need in our documentation, we have other resources available to help you. See Getting help.
Was this helpful?