Thanks for the 
service, @Marie! 
The minimalistic design approach that we fell in love with and expect from Asana long-term is at risk with these decisions to force features upon users like this.
I feel like we lack some organization, team, or project setting to define how the task layout should be presented as standard. Why not treat it as a custom field, with a customisation option to show dependency as standard or not?
Related unexpected design decision
This is related to the same unexpected design decision to show all custom fields from the parent on subtasks as standard that you forced upon us this summer. On a desktop, they are hidden as standard(ok), but not on mobile. Our members primarily working from mobile now need to scroll past 20 unused(blank) custom fields on the majority of their task.
The minimalistic, clean experience is gone.
It’s bad UX to force these additional fields upon all users instead of user customisation options to maintain the minimalistic design approach and open layout options for those who need it in specific cases.