Misleading truncation of nested entities in list view

I find this severe enough to post it as issue.

Current behavior:

  • List views are by default ‘truncated’ to show a limited amount of entities.
  • With more than x items, a button at the bottom shows ‘Show all xx’

Problem case:
When entities are nested in a list view, the list is truncated in an unexpected way:
The truncation does not take into account the nesting and top level entities in the nesting.

For example:

The nested list actually has multiple top level entities, but only one top level entity is shown.

I have to click the 'Show all xx" button, and then I see:

Desired behavior:

First solution:
By default the list view should display x items, starting with and including the top level items.

Better solution:
Ideally I would like to propose that a list view by default displays ALL top level entities if they have children, and NEVER hides them from display.
Why? Because truncation is for loading efficiency and its very unlikely/uncommon that a list view has more than 100 top level entities with children. So its safe to always show all of them by default.

5 Likes

I agree. I had a number of tasks that were ‘missing’ from my project management page that were actually there but I couldn’t see them unless I clicked show all - which caused scheduling of individual tasks issues as I couldn’t see all that were open.

What I find even more weird is that there were only 5-6 tasks within that parent but because they were lower on the overall tasks list of the project the system automatically hid them.

2 Likes