Why does the 'Progress (story points)' field include sub-tasks in the unestimated metric?

[Jordan Job]

When calculating the Unestimated issues metric, the Progress (story points) field takes into account standard issues and sub-tasks. 

In the example below, you can see that I have three standard issues under the Test Epic 1. All three have been estimated. And yet the Unestimated Issues field indicates I still have 3 unestimated issues. 

One of the unestimated issues is the epic itself. The other two are unestimated sub-tasks under Test Story #1. 

Almost every team I've worked with estimates product backlog items but not sub-tasks, so it's very unfortunate those are factored into the Unestimated issues metric. Is there a method to remove sub-tasks from being calculated in this metric?

Also, it seems like the Unestimated issues may just be buggy given that the Progress (issues) field only shows 3 issues. It does not factor in the epic itself or sub-tasks, which is how I would expect a progress metric to be calculated given that's how 90%+ of teams work.

[Amanda G]

I'm running into this problem now - where sub-tasks are being included in the 'Progress (story points)' calculations. We don't point sub-tasks, so it's confusing and throws off the progress stats.  Is there a fix for this?