@Oshyan , sorry for the delay in getting back to you. I’ve actually been playing around with the entity views quite a bit and they are really powerful. And because of that power, I think our expectations keep getting bigger 
One example is tasks associated with a project. Currently, you might be able to use a list view to see all the tasks (and possibly subtasks) in a hierarchical view. However, if you wanted to have a list view that groups and organizes the tasks by their state/workflow or people they are assigned to, you can’t do that with the list view. The only options I can think of are to:
- Sort list by those columns to at least get the same items together (and then scroll to the right section), or
- Create multiple list views that are filtered and sorted in particular ways. These would be static lists (difficult to maintain) and would be impractical if you have too many combinations.
- Use a board view to put things into bins. However, in board view you can only use one field as the bins whereas a list/hierarchical view can give you multiple levels of grouping. So you can group by status first and then be assignees.
I think the setup that @calh-fsp showed in this post, would be another example:
In that example, this structure had to be built by hand and when you add new status types, then you will need to ensure that new smart folders are created.
Ultimately, I think hierarchical views (and smart folders) might currently too rigid in how the users can define the levels which actually limits their usefulness (see also my prior discussions on multi-level recursive lists and here).