Nice. That's a definite improvement on the grouping. And the sort is much closer too. Here's what I get with the same query I posted above:
Quote:
- @due(2013-04-16) @context(Tasks)
- @due(2013-04-16) @context(Tasks)
- @due(2013-04-26) @context(Tasks)
- @due(2013-04-29) @context(Tasks)
- @due(2013-05-01) @context(Tasks)
- @due(2013-05-02) @context(Tasks)
- @due(2013-05-10) @context(Tasks)
- @due(2013-05-13) @context(Tasks)
- @due(2013-05-17) @context(Tasks)
- @due(2013-05-17) @context(Tasks)
- @due(2013-05-17) @context(Tasks)
- @due(2013-05-18) @context(Tasks)
- @context(Tasks)
- @context(Tasks)
- @due(2013-05-20) @context(Tasks)
- @due(2013-05-21) @context(Tasks)
|
If only there was a way to put the items without a due date after all of the items with a due date, then it would be sorting in the same way that OF sorts in this kind of view (i.e., you see stuff with due dates first and then stuff without due dates after that--not sure how the items without a due date are ordered in OF, perhaps by project?)
Presumably the tasks without due dates sorted where they did, because they get today as the due date, yes? Would there be any way of using the day after the latest occurring due date in the found set as the due date for items with no due date? That would place them at the end of the list, wouldn't it?