View Single Post
Thanks for the response, that worked. So either setting a project's overall due date isn't meant to be the shortcut that I thought it was, or this is a bit of a bug that prevents it from being a good shortcut. I keep getting the feeling that I'm simply using the tool wrong - is there a good reason to not assume that a task's due date is it's project's due date unless otherwise noted?