I’ve figured it out. Another data architecture issue, whereby tasks can have conflicting inherent attributes and the behavior is not well coordinated between them, combined with variable groupings (or lack thereof) among the Today/Upcoming/Later sections depending on type of sort. The conflicting attributes in question are Today/Upcoming/Later vs Due Date. E.g., note that having a Due Date equal to today’s date is not the same as being marked for Today. Asana data architects have chosen to have the assignment of a Due Date override the assignment of of a T/U/L status. The Due Date sort appears in this order:
- Any task with an assigned Due Date, sorted by Due Date, earliest first
- All tasks without assigned Due Dates, under headings Today, Upcoming, and Later
- Within the T/U/L headings, I see that Later has also been sorted by project - Today hasn’t (not sure about Upcoming)
So yes, we wanted sorting, but TBH I wanted it to be a bit more controllable and predictable. :-/
The actual list of unique tasks (for me) totalled 39 as of the time I ran my experiment.