# \[FIXED\] Ordering for Unsorted Entities

**URL:** <https://community.fibery.io/t/fixed-ordering-for-unsorted-entities/6086>\
**Category:** Bugs & Issues\
**Created:** [April 16, 2024, 11:02pm UTC](https://community.fibery.io/t/fixed-ordering-for-unsorted-entities/6086 "2024-04-16T23:02:46Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![interr0bangr](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/interr0bangr/32/8089_2.png) [@interr0bangr](https://community.fibery.io/u/interr0bangr)\
**Post date:** [April 16, 2024, 11:02pm UTC](https://community.fibery.io/t/fixed-ordering-for-unsorted-entities/6086/1 "2024-04-16T23:02:46Z")

</div>

Not a bug (I don’t think) but an annoying little issue I figured I’d bring up.

We like to sort many things in the list view by dates (ascending), where the oldest thing is at the top of the list and the newest thing is at the bottom.

For example:

Entity 1 - Jan 1  
Entity 2 - Feb 1  
Entity 3 - Mar 1

Now, when a new entity is created and its date hasn’t been set yet, I want it to show up at the bottom of my list, but instead it always shows up at the top.

So, expected:  
Entity 1 - Jan 1  
Entity 2 - Feb 1  
Entity 3 - Mar 1  
Entity 4 - NO DATE

but what I see:  
Entity 4 - NO DATE  
Entity 1 - Jan 1  
Entity 2 - Feb 1  
Entity 3 - Mar 1

It might be just me, but I would assume any undefined value should be LAST and not FIRST in a list that is sorted by ACCENDING. Basically, if something can’t be sorted, by default, display it at the bottom of the order instead of the top.

Clickup, as a comparison, treats it the way I expect it to behave where anything that cannot be sorted is always at the bottom of the list.

 ![Week-70-4-29-5-5-Human-Code-List-](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d1ccb326c2c821d949ec6003e7de9040cf4060b2.jpeg)

---

_[View the full topic](https://community.fibery.io/t/fixed-ordering-for-unsorted-entities/6086)._