Data Model Hierarchy with filtering at both levels

Hey everyone looking for guidance/suggestions on how to accomplis this. I am working with our companys underlying jira dataset. The problem we are facing when constructing the data model is the following.

We have the the top of the hierarchy which is an Epic and every other possible issue as a child. On the child table (jira all_issues) we attached an epic key that will navigate to the top of each issues hierarchy and say what epic each issue belongs to. However at the end of the day an epic is also technically an issue.

The business case problem we are running into is that we want to be able to filter by the properties that all issues have but at both levels of the hierachy. The example being we want to look at epics that are scheduled on our internal roadmaps by filtering labels at the epic level (jira epic_labels - > epic summary) and have that apply down to the jira all_issues table. However we then would want to look at all issues after that and filter by their labels (jira issue_labels -> jira all_issues). Maybe we want to look at specific teams. The data model as is doesn't allow the filtering to happen with ease and am unsure if there is a better best pracitce to accomplish this. 

Turning on filtering both directions between Epic Labels -> Epic Summary -> All Issues seems to work but wasnt sure if anyone had suggestions on a better way to data model it.