The Due date field is a little TOO restrictive.
As I am importing various Projects lists, they have "TBD" and "ongoing" in the due field. Which throws an error.
What is an elegant solution to a nomadic or yet-to-be-determined due date???
thanks
b
The Due date field is a little TOO restrictive.
As I am importing various Projects lists, they have "TBD" and "ongoing" in the due field. Which throws an error.
What is an elegant solution to a nomadic or yet-to-be-determined due date???
thanks
b
Hey Bryan - good call. I too have been a TBD addict all my life. Heh, I'm going to make a ticket for this to see what is possible. In the meantime, obviously, leaving the Due date blank is the only option...
yeah blank is my default TBD now.
But ongoing???
Hmmm... wondering what the difference is between 'ongoing' and 'TBD' for the End Date of a Task. Neither of these scenarios have an end date. I think by default, not having an end date assigned would indicate TBD. So perhaps the solution here is adding a flag in another checkbox column to track Tasks that are ongoing. Not sure that's right though... any other thoughts?