There are several threads dealing with the sense and the falling rock design of the red numbers indicating the amount of overdue/due soon tasks.
I think not only the red numbers but also the applied task styles (red and orange) are worth to be discussed:
Depending on my filter settings I have to look at a task list with up to 6 different colors. That's too much tawdriness for my eyes.
Furthermore theses styles override other useful informations: I can't see anymore whether a task is a singleton or next or availalbe action cause they all have the same overdue/due soon style.
So, I 'd like to propose to apply the overdue/due soon styles exclusively to the due date itself in the due date column. If a task without an own due date becomes overdue/due soon by inheritance from its superordinated project the project's dimmed due date should be placed in the due date field (same behavior as flags show).
What do others think of this?
I think not only the red numbers but also the applied task styles (red and orange) are worth to be discussed:
Depending on my filter settings I have to look at a task list with up to 6 different colors. That's too much tawdriness for my eyes.
Furthermore theses styles override other useful informations: I can't see anymore whether a task is a singleton or next or availalbe action cause they all have the same overdue/due soon style.
So, I 'd like to propose to apply the overdue/due soon styles exclusively to the due date itself in the due date column. If a task without an own due date becomes overdue/due soon by inheritance from its superordinated project the project's dimmed due date should be placed in the due date field (same behavior as flags show).
What do others think of this?
Threaded Mode