Tasklist sorting by date and prio
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zim |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This bug is with the interaction of tag filtering in the left pane of tasklist and sorting subtasks.I think the bug is easiest to describe by example. With the following test case put in a single notebook, I get a reproducible sorting bug in windows 8.1, zim 0.62 (haven't tested linux yet):
() Parent A @test
() Subtask A1 [d: tomorrow]
() Parent B @test
() Subtask B1 [d: next friday]
() Subtask B2 [d: today]
If and only if I have the @test tag selected in the tag list, the sort comes out like this:
Parent A @test
Subtask A1 [d: tomorrow]
(A subtasks)
Parent B @test
Subtask B2 [d: today]
Subtask B1 [d: next friday]
Note that parent A comes first, despite Parent B having the more urgent due date. (This isn't a user error with sorting ascending/
Without the test tag selected, the sorting result is as expected
Parent B @test
Subtask B2 [d: today]
Subtask B1 [d: next friday]
Parent A @test
Subtask A1 [d: tomorrow]
(A subtasks)
I think it makes more sense to sort the parent tasks by date of most urgent subtask regardless of whether a tag filter is being used or not.
summary: |
- Tasklist sorting by date + Tasklist sorting by date and prio |
I believe this is not strictly due to the tag filter. It is a inherent issue in the sorting that becomes apparent by the tag filter.
Key is that the sorting of the parents does not inherit the data or prio of their child items. This should be improved.
- Of parent items with equal prio, item with highest prio subtask should be on top
- Of parents with equal (or no) date, item with earliest subtask should go on top