Describe the bug
So basically i have a task manager in in which i have status relation with checkbox type to check done tasks. I use this relation instead of the inbuilt action template becoz it gives me the flexibility to dump my checked tasks to the bottom of my sets automatically with the sorts so that done tasks are no more in my eyesight. Now i have a due date relation too, so that the tasks which have been dued today automatically appears to my TODAY view becoz of the filter i have applied. Now, i want my chehcked tasks to appear at the bottom of my sets and the due dates with the most recent time to appear at the top( I use the time with date too so that i get to know which tasks do i have to complete first). Becoz i want to merge two sorts in one view, this bug wont let me. What happens is if i place status with sort ASCENDING and then 2nd sort of due date with lower priority of ASCENDING, it should technically give priority to the status first and thus should accumulate all the checked tasks at the bottom and then the priority to due date with all recent tasks to be done to be accumulated at the top. But im not able to achieve this, only the status or the due date sort works one at a time. Whats the problem you can see? If i apply status’ sort as first priority, then the due date scatters with no proper order in the set even if i have the due date with ASCENDING sort on, and vice versa if i apply due date as the first priority. I HOPE IM MAKING SENSE lol
To Reproduce
Just follow and apply filters and sorts asmentioned above and you will see the bug
Expected behavior
I want both the sorts to work with the priority as mentioned in the sorts column
Hi @Ishaan, I believe there are some issues with sorting, mainly with Status Relation Type and Tag Relation Type. No other topics include issues with the Checkbox Relation Type, so this is a good one to be added! Thanks for posting
It’s “ready to dev” as of a few weeks ago. I’ll do my best to keep it updated, but please feel free to follow up or share additional captured encounters so I can update the issue.
I am now on .34.3 and this still seems to be an issue, see the attached screenshots where the item “NW” doesn’t change place when the sort order changes from Ascending to Descending. Whilst this is shown with the second sort on “Status” it is the same if the second sort is changed to “Name”. It appears as if this task has a “Done” value between ticked and unticked since it goes away if you remove the “Done” sort.
When I link a task to a collection (for ex. from a graph view), it always appears on top of a collection and all sorting is ignored. Maybe app should apply sorting each time I open a collection? Or maybe linking to a collection should trigger sorting?
Also, as collection may be sorted manually, maybe a new sort criteria called “Manual sort order” may be added?
Hmm. I don’t find that to be true. I created a new task “Dummy Task” then linked it to a collection I already had and it followed all the sorting rules for that collection.
