Originally Posted by Craig
Well, I was just disappointed to find that a sequential project with a due date attached to a later action does NOT make the preceding actions due, too. That is, given this:
Project: apply for grant (seq)
- pick up forms @errands (no due date)
- fill out forms @work (no due date)
- turn in forms @errands (due 10/1)
If I viewed my available actions by due date, "pick up forms" would show up as having "None." This is technically correct, but means that the actual urgency of this project won't show up in context view until the last action is up, which may be too late!
I made a suggesion some time ago that might also help in this type of situation. I called it cascading due dates, but perhaps relative due dates would be a better description. I think it would be useful, especially for templates or for projects that have on a specific due date around which everything else in the project revolves, such as a conference.
The idea is as follows:
-- The due date for the project as a whole or for a key action in the project is set to a date certain (i.e., 18 July 2008).
-- The due dates for related actions are set as relative dates (relative to the project date or key action date), for example: two days before, two weeks before, three days after, three months after, etc. (similar to how repeat dates are set for individual actions).
-- Then, if the date certain (the due date for the project or key action) changes, the other related due dates change automatically.
This would avoid having to change all of the due dates for the related items individually, which can get very time-consuming, especially for repeating projects.