The Routine task at the top of the list is separated from the Routine tasks at the bottom because it has a time whereas the others do not. Because it has a time, the first sort criteria (due date/time) is triggered first.

The Routine task at the top of the list is separated from the Routine tasks at the bottom because it has a time whereas the others do not. Because it has a time, the first sort criteria (due date/time) is triggered first.

Ahem... I'm sorry, but the first sort criteria DID get triggered FOR ALL THOSE TASKS. As you can see, they're all grouped under "Due Tomorrow".

What happened, I think, is that (because there was a "due time" specified?) the first task got segregated or put aside and the two subsequent sort criteria did not operate on it...

That's NOT how sorting is done.

Or, the documentation should draw our attention to the fact that if "Due Date" is chosen, AND "Due Time" is not blank, here's what's going to happen, sort-wise...

Honestly, I can't think of any reason (from my standpoint as a user, as opposed to the programmer's standpoint) why the field "Due Time" should play any role in a sort based on "Due Date", "Context" and "Priority"!

If you sort by "due date/time" tasks due sooner in the day will come before tasks due later in the day?

Tomorrow at 9am Folder A
Tomorrow at 2pm Folder B
Tomorrow at 5pm Folder A

I think it would be more clear if all your tasks had a time. The fact that only 1 does is what is making it a little confusing. Tasks with a time come before tasks without a time and then task that have the same date and time are subsorted by your second criteria.