When sorting tasks based on priority, the tasks with empty priority values are also included in the sort (and it looks like they are assumed to have a value of zero). When sorting based on ascending priority, the tasks with empty values come first, which is not expected behavior.
To Reproduce
Steps to reproduce the behavior:
Create a set of tasks and add a few tasks
Give priority to a few tasks and leave the rest empty
Sort based on priority - ascending.
See the empty priority tasks at the top
Expected behavior
Tasks with empty values should not be part of the sort. More generally, when objects are in sets, the ones with empty values should be excluded from the sort and placed at the bottom.
System Information:
OS: Arch linux
Anytype Version: 0.29.0 (reported in 0.19.9)
Additional context
I am describing a specific problem with task set here, but I think it applies generally to sets of objects.
Same issue with date sorting. E.g., if one wants to sort tasks by date in an ascending order to put the most pressing tasks upfront, tasks with no due dates show up first instead of last.
Hello everyone. We will introduce ability to choose between several options of sorting later. But for now it is considered to be intended way of work. If this topic will receive significant amount of votes we will increase priority for this one
Any chance you reverse this option, so showing empty values at the bottom instead, before you introduce the sorting options in the future?
This very minor thing pretty much makes all of my workflows impossible since I if I want to add a sort, I need to make sure that every object has something in that relation or else the empty ones will bubble at the top and make the relevant objects show up at the bottom.
