# Unexpected behavior when adding nested entities

**URL:** <https://community.fibery.io/t/unexpected-behavior-when-adding-nested-entities/10153>\
**Category:** Bugs & Issues\
**Tags:** table-view\
**Created:** [December 11, 2025, 6:31pm UTC](https://community.fibery.io/t/unexpected-behavior-when-adding-nested-entities/10153 "2025-12-11T18:31:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_Grattan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/john_grattan/32/13283_2.png) [@John\_Grattan](https://community.fibery.io/u/John_Grattan)\
**Post date:** [December 11, 2025, 6:31pm UTC](https://community.fibery.io/t/unexpected-behavior-when-adding-nested-entities/10153/1 "2025-12-11T18:31:02Z")

</div>

I have two databases: tasks and subtasks. The relationship is such that a task can have many subtasks, while each subtask is associated with one task. I created a view to connect my tasks database and decided to nest subtasks under their respective tasks.

When I create a task and want to add a new subtask nested underneath it, there are a few ways to do this. One method is to right-click on the task, hover over “New,” and then click on “Subtask inside.” This opens a nested field for me to enter the subtask, which is great. After I fill in the subtask and hit enter, I can continue adding more subtasks.

However, I noticed that the field for adding another subtask appears above the subtask I just created. This behavior is unexpected because **I would expect the subtasks to be listed in the order I create them, not with the newest one at the top**. As a result, every time I create a task with multiple subtasks, I have to manually rearrange them to restore the order in which I created them. Ideally, when I hit enter to add a new subtask, it should appear below the last subtask I added, not above it.

---

<div class="post-metadata">

**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:** [December 11, 2025, 6:37pm UTC](https://community.fibery.io/t/unexpected-behavior-when-adding-nested-entities/10153/2 "2025-12-11T18:37:55Z")

</div>

This behavior was designed to survive long lists of subtasks, imagine you have 100 and clicked +, in this case system would scroll you down a lot and it can be weird

---

<div class="post-metadata">

**Author:** ![John\_Grattan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/john_grattan/32/13283_2.png) [@John\_Grattan](https://community.fibery.io/u/John_Grattan)\
**Post date:** [December 11, 2025, 6:38pm UTC](https://community.fibery.io/t/unexpected-behavior-when-adding-nested-entities/10153/3 "2025-12-11T18:38:42Z")

</div>

Okay, that makes sense. Am I the edge case? Could we have an option to control this behavior?

---

<div class="post-metadata">

**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:** [December 11, 2025, 6:39pm UTC](https://community.fibery.io/t/unexpected-behavior-when-adding-nested-entities/10153/4 "2025-12-11T18:39:01Z")

</div>

We’ll think, since the problem is real

---

<div class="post-metadata">

**Author:** ![John\_Grattan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/john_grattan/32/13283_2.png) [@John\_Grattan](https://community.fibery.io/u/John_Grattan)\
**Post date:** [December 11, 2025, 6:39pm UTC](https://community.fibery.io/t/unexpected-behavior-when-adding-nested-entities/10153/5 "2025-12-11T18:39:20Z")

</div>

Thank you!