Time included in sort when using a date relation

Describe the bug
When sorting by date, time is also taken into consideration even though I haven’t checked the include time checkbox.

Expected behavior
I expected the time not to matter when it comes to sorting by date, especially when it’s not shown to me in the set.

System Information:

  • OS: Win 11 Pro
  • Device Manufacturer/Model: Dell G3 3590
  • Anytype Version: e.g. 0.24.0

Still reproducible on Windows 11 @ v0.38.3 alpha.

Sorting objects by date still takes time into consideration despite the toggle for “Include time” is off.

Sorting objects by date while including time (ascending) and then by name (ascending), gave me this mess:
image

Name = left column and Due date = right column… Neither name nor Due date follow an ascending sort.

Hi @Filip, thanks for sharing this bug report. Is there any particular reason for NOT taking the time into account? I’m trying to think where it is important that Objects in a Set are ONLY sorted by date, ignoring the time. Maybe when there is a secondary sorting rule active, but I don’t think that is currently supported…

There definitely would be a problem when you want to sort something by date and then by name or status for example. Time sorting would override any other sorting since there would be seconds as time is stored as timestamp.

We will consider fixing this in upcoming releases.

1 Like

Still reproducible on Windows 11 @ v0.38.3 alpha.

Sorting objects by date still takes time into consideration despite the toggle for “Include time” is off.

Sorting objects by date while including time (ascending) and then by name (ascending), gave me this mess:
image

Name = left column and Due date = right column… Neither name nor Due date follow an ascending sort.