Many best practices say, “Always set a Due date,” so is my recommendation to consider leaving Due date unset part of some new Forum Leader Tips > Heresy Edition subcategory?
I believe there are times to legitimately leave Due date unset, but only if you’re aware of the implications. For example, doing so won’t be compatible in a project or My Tasks view that’s sorted or grouped by Due date.
So when would it be appropriate to leave Due date unset?
For private tasks in your My Tasks, use your Today, Upcoming, or other appropriate sections to indicate when you should be working on a task and leave Due date unset (that’s not what Due date is for). If you do have a known Due date, by all means, set it, but urgency is not a due date. A good reason to set a Due date on a private task is to use a “Due date is approaching . . .” rule (aka task auto-promotion).
For public tasks in projects, leave Due date unset if you don’t know the actual due date, unless you have a clear team-wide protocol for using desired/hopeful due dates and a means for distinguishing them from actual requested or imposed actual (hard) due dates. (You may want to consider using Shift+Tab+F to create your own private follow-up task and set the desired Due date on that task instead.)
For a little more depth on the above points, and some broader related topics, see two earlier Forum Leaders tips of mine:
Thanks,
Larry Berger, Asana Services Partner, Trilogi Solutions