How to Resolve Inaccurate Issue Tracking in Reports Caused by the Inclusion of Epics?

[Shuo Ping]

The usual practice in reports is to track the changes in the number of Task or Bug issues. However, in our report, an Epic issue is consistently being included in the count, causing the total count in the report to be one more than the total count on the Jira board. For example, if there are a total of 50 issues, but one Epic is being counted in the report, the total becomes 51. How can we resolve this issue? Thank you.

[Trudy Claspill · Accepted solution]

Hello @Shuo Ping 

Are you using a built in report? If so which one?

Are you using a report that is based off of a filter you created? If so, show us the filter you created and the Epic that is getting included that you think should not be included.

[Shuo Ping]

Thank you for your response! We are mainly using the burnup report and sprint burndown report, and the project type is a team-managed project. We have not applied any filters to the reports; the Epic should not be counted into the total number of the issues. 

How can we remove the Epic from the total count so that the final outcome only contains the issues?

[Trudy Claspill]

Can you provide screen images that show that an Epic is being included in the reports?

As the Epic assigned to the Sprint for which the report is generated?

[Shuo Ping]

Thank you for your response. As you can see in the first image, the total count for all the issues is 50. However, in the second image attached (the totol issues counted in the report), the total issues have been counted as 51. One of the epic tasks was included in the report that we generated.  

[Trudy Claspill]

Thank you for that additional information.

Are you working with a Team Managed project or a Company Managed project? That information will be shown at the bottom of the navigation panel on the left when you are viewing the project board.

Did you set the Sprint field on the Epic to be the sprint against which you are creating the report?

Did you assign an estimate to the Sprint?

From the screen images it appears that you are using a Team Managed project. I was able to reproduce your scenario by assigning the sprint to the Epic and setting an estimate on the Epic. The Epic is then included in the Burnup and Sprint Burndown reports, but it is not included in the count of issues on the board.

You can solve this be ensuring you do not assign the Epics to Sprints.

[Trudy Claspill]

If the sprint has been completed you must reopen the sprint in order to remove an issue from it. 

You can confirm whether or not the Epic was added to the sprint by looking at the contents of the Sprint field in the Epic issue 

What have you set aside the Estimation Statistics for your board? Those are the values that are reflected in the charts.

[Shuo Ping]

Thank you for your information!
Here's the answers to your previous message :
1. We are currently working on a Team Managed project.
2. We did not set the sprint field on this Epic. 
3. We did not assign an estimate (currently the original estimate = 0h)

We tried using the method you mentioned earlier (without considering Epic) to solve this problem. After checking, we found that we didn't manually include this Epic in the selection, so we're not sure why it got counted in. Could you provide some information on how to manually remove this Epic from the scope? Thank you for your help.