Hello community,
I have the ask to create a new issuetype that is at the same level as an Epic, thus an issuetype that cannot be a child of an Epic.
My JIRA instance is utilizing Portfolio so I went into the hierarchy and set it up as such (Epic level Name has Epic/ Team Effort/ Maintenance), since we utilize Parent Link and Epic Link to define the parent child relationships:

thought that would do the job but I have noticed that on boards (backlog view) you can grab a team Effort or a Mainteance issuetype and you can drag it under an Epic effectively making it a children of the Epic.
We want to avoid this behaviour and not allow a team effort or a Maintenance issue type to ever become a child of an Epic.
Any input on this would be appreciate 
Thanks!
-Roberto