Is it possible to create a feture request to add a trigger to subtask created? That way we can use the rules to assign project to parent project
When someone at Asana Product Management gets around to taking a look at this and putting it on the roadmap, can that person please please PLEASE understand that we are not asking for any unintended consequences to be created? For instance, right now, any entity - task or subtask - that is “homed” to a Project will show up on the Project Timeline, and as a top level List item (row) or Board item (card) - in ADDITION to the fact that the subtasks are already associated with and accessible from their parent task. We DON’T want to simply add Subtasks explicitly to a Project and find them redundantly cluttering the Timeline, List, and Board views. Asana will need to provide more controls for views (e.g. toggle subtasks on & off, or collapsed vs. exploded) and/or better defaults for every view.
7 Likes
Vote vote vote!
4 Likes
really unfortunate Asana has not remedied this. Subtasks are a critical part of visual hierarchy but with all the limitations listed are nearly useless. had no idea they didn’t show in the calendar, and that they are assigned to “No Project” when in fact they are made within a project - Asana, please fix!
2 Likes
Any update on when this may be fixed? this is a huge issue for our team
We don’t have an update on this topic at the moment, but please make sure to upvote Allow to automatically add subtasks to project we’ll post an update on this thread as soon as we have an update on our end!
2 Likes