Asana definitely listens, I know this for a fact. They don’t react much because they are tied by the rule “we don’t share the roadmap”. The product has evolved tremendously in the past months, including some old topics being “finally” fixed, so I am really hopeful!
In some cases, a situation is not seen as a “bug” or something “to fix”. So I guess, it falls on the Product team and not the “Bug fixing” team, which in some cases can impact how fast it is developed.
Perhaps the solution would be to enable it the feature on an individual’s calendar. Yes, that would make it a bit more onerous to get used to, but I think the common consumer is tech savvy enough to figure that out. This would eliminate the problem of a subtask due date cluttering other people’s calendar. Maybe just find a way to integrate Google Calendar’s process or mimic somewhat to allow for ease of learning. But, quite honestly, I bet that if you took a survey of your millions of users and asked if they would be interested in an “Add Subtask to Calendar” function, the majority would want it. Just because it hasn’t been upvoted into the millions here doesn’t mean that the others don’t want it. It just means they may be too busy to come and post. Or they have decided it isn’t worth their time and moved over to different software… 
Hi,
I have some requests to make to evaluate the possibility:
The calendar view, starting from the projects, does not show the subtasks and I would like to be able to view them.
In the calendar view on the whole team I would like to be able to insert the possibility of not displaying subtasks, due to the large number of tasks present in this view.
In the calendar view I would like to be able to insert the name of the project and not just the relative color.
Thank you and regards
Hi @Ivano_Iodice welcome to the forum.
Merging this with the existing request for subtasks on calendar under the product feedback section. For each of your other asks please search for exisiting posts or create a new one under the product feedback section of the forum.
I would just like the option of having subtasks in the calendar format - for me to toggle on and off depending on when I want to see them. Without the functionality of creating templates for sections, you have to rely on subtasks instead. And working interdepartmentally, having a lot of individual tasks that should inherently be under a task but not being able to see the time capacity/ calendar of those individual subtasks is a HUGE hurdle. It may not be for everyone, yet make it an option for the people who desperately need it.
Team,
Please let me offer a compromise here. Please give us a field at the top of all Project Views that says “Include Subtasks” so that we can manually toggle this on/off as needed.
I totally see why many users wouldn’t want subtasks showing, so I don’t want to see Asana wrecked for them. However, we are definitely on the other side of that fence.
Our entire company is hindered because we have no way of showing Subtasks on Calendar/Board/Timeline views. This is a titanic level hassle for us, causing us to do tremendous amounts of multi-homing with Task and Project Templates.
To add insult to injury, recently Asana has changed something in the background where you can no longer make a Task Template wherein the Parent Task and Subtask all live in the same Project. That WAS my workaround to allow all our subtasks to show up in the same Views. Especially Calendar view.
Now, when you make a Task Template, if you have everything homed in the same project (parents and subtasks), the moment you convert it to a Template, the Subtasks are removed from the Project. When you launch the Template, none of the subtasks will show up in the Project, and thus none of them in the Calendar.
I was very much disappointed to see this.
But, we would NOT need to do any of this, if we simply had a toggle at the top of the page that said “Show Subtasks”. That would solve it all!
Could there be a function for a calendar and or timeline view per task? I would love to be able to have a visual of subtasks.
Hi @Camille_Whitson There is currently a product feedback for this. I suggest upvoting it.
Where?
How many upvotes before development happens? It seems like this has been open for 5ish years.
The number of votes is taken into account but isn’t enough to trigger a development, that’s not how product development works. Otherwise an app would become some kind of a Frankenstein where the crowd drives the development without a clear vision.
You mean, like [insert name of favorite app to beat up on here]*?
Thanks,
Larry
* I chickened out of naming one!
Well you can name Salesforce for one, they decided to make it heavily customisable. Meaning you now need an expensive consultant for 6-months before being able to do anything 
The Asana Product team has an amazingly hard job: keep the product simple (people praise its simplicity) while adding new features…
Adding my vote to this also. I think we represent a fairly common user experience where we have Tasks and Subtasks that ladder to a specific request. We would like to view the Subtasks on the calendar and NOT the parent task or other associated tasks.
A good example is for email production – we only want the subtask for Send Complete to show on the calendar. We cannot filter the Calendar view to Subtasks and adding a custom field to the Subtask doesn’t work either since Asana doesn’t look for Subtasks in the Calendar view.
Filtering by a Custom Field like “Planned Send Date” also doesn’t work because it shows the full working time for the email development Parent Task which can be multiple days/weeks. (Also only allows to view specific time frames or “after today” which isn’t helpful for a full month view.
@TheAnswerLady - I moved your post to a more relevant thread. Make sure you upvote it using the button near the title!
In the meantime, subtasks can be multi-homed into projects (including the same projects as their parents), so perhaps this could be a temporary workaround for you?
Thank you, Stephen. I have tried that and unfortunately, it doesn’t work right unless I do that manually.
Using Rules, the options are:
I’m not sure of a great way to do it via automation (confirmed the limitations you mentioned; for point 2, the available variables are limited for subtask naming and you can’t get subtasks to auto-inherit parent field values, to my knowledge).
Something you could try is using some kind of trigger (maybe a single-select field?) on subtasks with a rule action of “move to section”. If that fires on a subtask, “moving to section” will actually multi-home the subtask to that section of the project. It’s definitely a workaround more than a solution, but maybe something to try.
Thanks for the suggestions! This is what we have been doing for now, although it is still manual. There is not currently a way to write a rule to run on Subtasks only so the initial field change trigger has to be done manually in order for the Rule to ‘see’ the change.
You’re correct that Subtasks don’t inherit all of the values of the Parent Task, but it is at least helpful to see the association (in the task name with the “<”) and if you’re using a Rule to create a Subtask, you can actually force the inherited characteristics via the Variable Data tags. The Rule that I was testing carried over the task title by using the Name tag and the description details by using the Description tag – that works fine if you’re keeping it as a Subtask. But if you add the Project/Section, it will create a new task and abandon the variable tags.
Wow just tested this for myself and am seeing the same thing…that definitely seems like unintended behavior, as the resulting task is still a subtask…
@ambforumleader - anyone else encountered something similar? TL;DR - using variables for naming in the “create subtask” rule action seems to break when that subtask is multi-homed to the parent project (haven’t tested with other projects). I don’t see any other threads on this.
