Issue Summary

Adding issues to a parent on the top-level hierarchy results in a messy list view. Trying to create sub-tasks results in an even bigger mess.

Steps to Reproduce

1. Assume you're using an issue hierarchy that consists of a top-level issue (let's call it TOP) and another issue type on the same level as Epic (let's call it BOTTOM).
2. Create a JWM project using the "Project Management" template.
3. In the list view, create 2 TOP issues and 2 BOTTOM issues.
4. Using the "Parent" field, mark any of the TOP issues as parent of the BOTTOM issues.
5. Try to create a sub-task for any of the listed (BOTTOM) issues and observe the atypical behavior.

Expected Results

For step 4 - The BOTTOM issues should disappear from the list view and should be only visible if you expand the dropdown next to the TOP issue.

For step 5 - You should only see one field to enter the name of the sub-task and be able to see if directly after it's created.

Actual Results

For step 4 - You'll already notice that the BOTTOM issues don't disappear from the list view and are visible twice if you expand the TOP issues.
For step 5 - You'll notice that the field allowing you to enter a name for the sub-task is listed twice, and you won't be able to see the sub-task created until you refresh the page

Workaround

Refresh the page (list view) after each action.