[curt.clifton]

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!

[Submitted via feedback.]

Craig,

You probably know this, but for other readers the solution is to set the due date of the parent project to 10/1. If you have additional actions that happen after 10/1, then you can group the actions leading up to the deadline into an action group:

Project: apply for grant (seq)
- Completed application (due 10/1)
--- pick up forms @errands (no due date)
--- fill out forms @work (no due date)
--- turn in forms @errands (no due date)
- From funding agency, update on grant status (no due date)