Quote:
Originally Posted by CatOne
The problem here, of course, is that if you use "due soon" or "due or flagged" perspectives, the start date is really worthless; they're displayed anyway.
|
Ah, but when I look at the "due" perspectives I
want to see what is due, even if I can't (or don't want/need to) work on it yet. Looking at my due lists right now, I am having trouble seeing why I would want it otherwise, though perhaps my habit of only using the time-based groupings with the due views is responsible for that viewpoint.
I run with "Due Soon" set to 2 days, and start the day off with a look at a context mode view, due soon, grouped by due, sorted by due, which gives me a reminder of anything that is going to be time-critical. Then I'll look at a context mode view, available actions, grouped by start, sorted by project, to see what new items have become actionable today. A quick change of the flagged item selector in that view will let me see anything out of the union of (due soon | newly available) that has been flagged in my reviews for attention. This seems to work well for me, but your mileage may vary, as they say.
I can see that one might reasonably want the other behavior (obey start dates in due views), but it seems to me that the people who like the current behavior would be unhappy with the proposed behavior, and even if one wanted it some of the time, all of the time wouldn't be desirable. I don't see an clean, easy way to classify/specify a subset of actions/projects that would get the proposed behavior, do you?