I think we both agree Asana can’t decide that suddenly subtasks due date are linked to parent tasks, because in many cases you might want to have different dates on the parent than the subtasks, or at least have the freedom to do whatever you want with subtasks.
Your follow up argument is one that is very often use: “Let’s put a checkbox and let people decide”. I don’t think that’s a good idea. And you probably realised by now that Asana almost never made that choice. If you do, you end up with something like Salesforce or Wrike, where a ton of stuff is customisable, you need a consultant for 6 months to set up something, and on a daily basis you have different behaviours you don’t understand anymore.
Most of our clients praise Asana for its simplicity and yet its ability to be flexible. What I understand is that you are ok with having Asana a bit more complex to setup in order to be more powerful. I am not sure Asana will (or has) made that tradeoff…
Note: I do not work for Asana, I used it for the past 10 years and my team and I helped 500+ clients deploy it, so we tend to have a “broader” view of how clients approach the tool and how Asana usually approaches feature requests
Don’t get me wrong: I sometimes wish Asana designed subtasks differently from the start. A long time I decided to dedicate my energy to find ways to use Asana the way it is.