Unexpected behavior when adding nested entities

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.

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

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

We’ll think, since the problem is real

1 Like

Thank you!