# Sub Types - suggestions, or new feature? **URL:** \ **Category:** Ideas & Features\ **Tags:** flexible-domain\ **Created:** [June 22, 2020, 1:22am UTC](https://community.fibery.io/t/sub-types-suggestions-or-new-feature/791 "2020-06-22T01:22:25Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [June 22, 2020, 1:22am UTC](https://community.fibery.io/t/sub-types-suggestions-or-new-feature/791/1 "2020-06-22T01:22:25Z")
Hi Guys, You have talked about hierarchy views in Twitter, Medium, etc. as a focus of your current Roadmap. I could really use this as I move along in Fibery. Being able to create one’s own hierarchy I think is a key aspect of a no code tool that should be available. It’s a cornerstone of Notion in fact. And a big piece of the popular work management tool Wrike. I have had trouble making a hierarchy in Fibery as I think the suggested solution is to create a new type, and then a “many-to-one” relation. I have spoken with the team about using a relation to make a “one-to-many” within a type, like this: ![Image 2020-06-21 at 9.16.47 PM.png](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d90ff2ce80a57a4853949a31b5589e2ef56e5d48.png) But I had some issues with the left menu and folders rendering correctly, which I think is why the team suggested to me I don’t do this. Have you thought about the ability to simply create a “sub-type”? This would help me tremendously, as I have many things that I’d like to set up on a multi-hierarchy level, and not be limited. At times, two levels of hierarchy are sufficient, but others I might want to go 5 deep. It would greatly simply my Fibery set up if I could just make some sub-levels within a type. Thanks guys! ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [June 23, 2020, 6:50am UTC](https://community.fibery.io/t/sub-types-suggestions-or-new-feature/791/2 "2020-06-23T06:50:30Z")
The solution here is to just support self-reference relations well. We did not pay enough attention to that, but with Hierarchy View release we will. ---
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [June 23, 2020, 4:19pm UTC](https://community.fibery.io/t/sub-types-suggestions-or-new-feature/791/3 "2020-06-23T16:19:51Z")
Michael, that’s great to hear you’re thinking that way! I have really studied a ton of work management and issue tracking apps out there, and the way TargetProcess handles this is about the best I’ve seen. So assuming that was something you were behind back when it was released 😉 I have high hopes for what you’ll come up with for Fibery! This is a huge need I have to move forward in the evolution of my Fibery set up, so if you feel inclined to preview anything whenever you have something to show, would love to see it…Kind of like when you gave us a taste here: > [@Reciprocal reference when using "/" commands in entities](https://community.fibery.io/t/reciprocal-reference-when-using-commands-in-entities/365/11): > > WIP Cheers and thanks again! ---
**Author:** ![Jean](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@Jean](https://community.fibery.io/u/Jean)\ **Post date:** [June 23, 2020, 6:43pm UTC](https://community.fibery.io/t/sub-types-suggestions-or-new-feature/791/4 "2020-06-23T18:43:23Z")
I would also love some roadmap updates 🙂