# \[DONE\] Tree diagram AWOL **URL:** \ **Category:** Bugs & Issues\ **Tags:** whiteboard\ **Created:** [May 2, 2021, 5:14pm UTC](https://community.fibery.io/t/done-tree-diagram-awol/1598 "2021-05-02T17:14:22Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [May 3, 2021, 10:24am UTC](https://community.fibery.io/t/done-tree-diagram-awol/1598/3 "2021-05-03T10:24:11Z")
Shame ☹ As I recall, the whiteboard diagram was able to represent links between entities of the same type when the relationship wasn’t 1-to-n, something which the hierarchical list can’t do. Maybe I’m misremembering… > [@Polina\_Zenevich](#): > > we will bring them back, but not in the nearest future That sounds not very promising - I had hoped that some of the needs for whiteboards would be in the pipeline: > [@Auto-Generate linked diagrams in Whiteboard](https://community.fibery.io/t/auto-generate-linked-diagrams-in-whiteboard/684): > > Hi Guys, I wanted to ask about the ability for Whiteboards to show existing entities in an App, or even Cross-App, as well as relations. In my use of Whiteboards, which is a big reason I’m using Fibery over other solutions, I’d like to be able to both “create” in a whiteboard, then convert to Types and Entities, but also show what I have already set up in my work structure that exists within apps. Thankfully, you have made great strides on the former - it’s possible to do a lot right now to d… > [@In Whiteboard, "Transparent" or "Empty" to represent Parent Entities](https://community.fibery.io/t/in-whiteboard-transparent-or-empty-to-represent-parent-entities/667): > > Hi guys, I’d like to ask if you could consider a aspect of Whiteboard where a parent entity could be viewed as an “empty block” or group around its children. Something like this: This is an image I did in reference to another work management app, but the point is that the “grouping” block would be the parent entity, with the “task” blocks the children. This is very useful for expressing software systems - tiers of development for example, or Master Features that contain many sub fe… Should we stop hoping for these? --- _[View the full topic](https://community.fibery.io/t/done-tree-diagram-awol/1598)._