If users are used to one kind of behaviour and another is asked for by many users I will never understand this common developers opinion to decide for one or another instead of giving options. Esp. when these minor options would not blow up the code at all.
From 6 to 7 a few things have changed without an option to keep the old behaviour, while other things have not changed or got a new option that have been asked for for many years. One size fits all? Of course not. So why not go for options as much as possible giving users a choice instead of trying to try to force a decision of a few (developers) over many (users)?
I find this really weird. When I add a new task, I don’t mean it has started. But it seems you have reasons for not changing that behavior.
However, may I ask why, when I enter a task from the top line of the task list the status is set to “waiting on someone else” but if I use Alt+N it is “Not Started” even though in both cases you automatically set a start date and time?
My preference is that new tasks are not started, but with a reminder at some time in the future.
Making these configurable defaults would make the task list feature more useful for me.