If a subtask is a milestone, the milestone symbol should appear on the subtask list within a task vs. having to click into the subtask to see that it is a milestone.
Hi @Ashley_Stauffer and thank you so much for taking the time to share your feedback with us. Iāve slightly modified the title of your thread so it better reflects your feedback and make this thread more discoverable for other users to vote!
Milestones are still pretty new, and weāre planning to improve them in the future so thanks for taking the time to share your thoughts with us! If there is anything else I can help with in the meantime, please let me know!
Sounds great, thanks @Marie! I was really excited for the milestone feature so was happy to provide feedback for the new feature to optimize how our team uses Asana. ![]()
Dear Asana developers and community.
This application is awesome and I love everything about it. Our agency uses it to sustain a high amount of productivity and fluency.
I just read on the Asana blog about the new Asana milestones.
These are awesome and offer a way to align our team towards short-term wins and provide nice visualization.
However, as an agency that operates mainly using subtasks, with the main task being used for overall project description, we cannot take advantage of the milestone visualization in the subtask area.
For instance, I have marked the āExample subtaskā as a milestone, but I do not get the nice green diamond that goes around it within the subtask view as I do with the main task view.

Thus, my request is this (and I think it should be an easy fix) can we get the nice green diamond to appear within the subtask view, so we can take advantage of the milestone functionality across the Asana platform.
This would really help out agency and I think others as well.
Thank you.
-Ian
Hi @iherzing
Thanks for sharing your feedback and providing us with context; this is super intresting for our Team!
We actually already have a conversation on this topic, so in order to gather all feedback in one place, Iāve merged your post with the existing one; hope thatās ok!
+1,000,000 for this update/functionality! Additionally, if a Subtask Milestone could somehow be represented on the Timeline view, which only shows āParentā Tasks that would be awesome as well. Perhaps a little green vertical line at the point where the Subtask Milestone occurs for a main/Parent Task that has a start/end date?
YES YES YES. Subtask milestones not showing up on timeline is a significant nuisance.
Hi, yes, please emphasize the importance of adding the icon for subtask milestones (as quickly as possible), so itās visually consistent with milestones used throughout the project! Thank you!!
Hello everybody , we are using asana for several clients and until now sounds great , thank you for your work and support.
I agree that this feature is highly necesary while most times milestones are in subtasks of a wider task or project.
We hope to have it soon ![]()
Best regads
Until this is updated in Asana, perhaps the following is of interest to some on this thread:
Thanks,
Larry
Iām disappointed that after creating a long workflow with milestones as subtasks that they will not show up on the progress card or in Portfolios!! What is the point if they are only shown on top level tasks?!
Any update on subtasks set as milestones showing up in portfolios/status updates?
MAJOR functionality bug.
Same feedback from me. We tend to use Projects as a scrum board for tasks of the same nature. For example, the content calendar I manage is populated with individual cards (main tasks) for each publication. Within the cards are the subtasks necessary for publication. The cards themselves arenāt really milestones simply because so many things out of our control can delay or re-order our publication schedule.
The ability to expand main tasks on timeline view to show the subtasks (and perhaps a āprogress barā for the main task?) would be very helpful in getting a big-picture look at where each piece is in the content process.
To use Milestones as Asana currently has them implemented, we would have to make a separate project for every. single. publication.
Not really practical.
Smartsheet gives the user much greater control over display and nesting, and is why in my previous job I selected it to manage content calendars. Granted, Iām no Asana master (although I do my research before posting here), but aside from some of the team communication features, the way we use it doesnāt differ very much from a Trello board, and Trello felt less cluttered.
Highly suggest Asana incorporate these relatively simple concepts to stay competitive with other project management software. Currently it feels like JIRA and Trello had a bright but easily distracted child.
Since I apparently canāt edit my above post, I wanted to elaborate on why better subtask functionality is important.
Smartsheet succeeds because ultimately you can take a given set of functionalities and use them to build, well, pretty much your ideal custom-fit project management system. Sure, itās a bit of a pain to begin with, but the tools are pretty user-friendly and there are many great templates one can adapt. Itās also a lot easier to pass content in Smartsheet to other applications, because everything, even if you hide the spreadsheet view, at its core, has a nice individual cell to call that is organized in a straightforward, logical layout.
Where I really see Asana stumbling is that rather than being built around a set of functionalities, itās built around a particular workflow, which seems to be following: Project ā Main Tasks ā Scut Work. As above, this is not a practical workflow for many kinds of tasks. Asana is essentially saying āthe Project requires the most attention, the Main Tasks reasonable attention, and the scut work (aka Subtasks) requires none at all.ā
However, as any healthcare professional will tell you, the scut work is often the most irritating and demanding portion of their workflow, and for Asana to essentially write it off, saying āHere are some icons to play with in your ball pit, they donāt do anything because all the big kids use Projectsā is a major misstep. Simply adding one more degree of freedom, either in the management of Projects or that of Subtasks would exponentially increase the number of workflows and managment styles it could support.
The TL;DR here is that Asana either needs to implement a āboard of boardsā functionality allowing Projects to be grouped, sorted, and reported on, or go the other direction and just make the existing, performative subtask functionality, well, functional, which Iād assume would be easier than a āboard of boards.ā
All they have to do is just toss us a few different view options for Main Tasks like they have for projects and weād be good to go.
Just to add that subtasks, which a marked as Milestones, are not visible either on the project āOverviewā page, under the section "Milestones.
I agree! You cannot have date ranges on Milestones, so I made the parent task a regular task and add a ācompletedā sub-task for the milestone - but then the Milestone doesnāt show up on the Overview tab. Which is kind of the point.
Just found this thread as I have the same issue, and am very shocked to see that this small UI change has still not been deployed after almost two years. @Marie please can we have an update on this? Not being able to see that subtasks are milestones surely makes the ability to make them milestones entirely useless.
The subtasks as milestones issue is still not being fixed. Wanted to use Asana for a very detailed project, but without this feature itās not going to be easy. Has anyone have a work around?
Hi @Carl_Peters and welcome to the Asana Forum!
I need this fix too. In the mean time I have to put an icon at the beginning of the milestoneās title, like a diamond icon ![]()
