+ Add Question

How is the task list for days organized?

Tasks with a due time are first, in chronological order - that makes sense. But I would like to know how the rest is organized. For example here's what Today has for me:

9am Project #2 task (priority 1)
10am Inbox task
11am Inbox task
Project #4 task (priority 3, starts with W, recurring)
Inbox task (starts with F)
Inbox task (starts with H, recurring)
Project #6 task (links to Gmail, starts with C)
Project #6 task (links to URL, starts with R)
Project #5 task (priority 2, starts with W, recurring)
Inobx task (starts with J, recurring)
Inbox task (links to URL, starts with R, recurring)

Aside from the chronological start, it makes no sense. It's not alphabetical by task, it's not alphabetical by project, it's not by priority, it's not seemingly organized in anyway.

Except that we're talking about logical computer programming so there has to be a method to the madness - what is it?

All responses

Arp Laszlo
Replied on Jan 17, 2014 - 14:02 UTC

Also it's not arranged by the organization of projects in the sidebar (that's what the project #s refer to).

David Trey  staff
Replied on Jan 17, 2014 - 17:27 UTC

Hello Arp,

If you're referring to the today or 7 days view, the order is:
- by date
- by priority
- by project (grouped, not sorted)

We're aware of an issue which breaks the priority and/or project sort, but we're unable to identify it's source (the trigger that causes it to get out of order for the first time).

We'll continue to look into and and will also release a big update soon which will hopefully fix this issue, but if it won't, we'd need to know what has to be done to trigger this bug to fix it :(

Best regards,

Arp Laszlo
Replied on Jan 17, 2014 - 19:37 UTC

Clearly something's off for me as I added a new todo to Project #2 with Priority 1 and it's inserted above 'Project #6 task (links to Gmail, starts with C)'.

Also, #4-6 are in a group and they are separated by Inbox tasks. Aside from the date/time, it's all wrong.

David Trey  staff
Replied on Jan 17, 2014 - 23:29 UTC


This seems indeed like the issue I've been referring to. Unfortunately, we have to find a way to trigger it at least once to identify the source of this issue. It seems to be quite complex and most likely not triggered by one specific action, probably by multiple.

We'll continue testing and trying to identify it.

Best regards,