Welcome, @Diana_Di_Leonrdo,
Probably. You can confirm about your plan with your Asana Admin or Super Admin or Billing Owner.
Re your suggestions, voting at the top of this thread helps, and adding your use case so Asana understands your need.
Thanks,
Larry
Thanks for this! I got the rule to run but it’s throwing an error - anyone else had success?
@Chloe_Hellerman - What is the error? I haven’t tested this script personally but from a quick skim it looks to be at least logically correct. They wrote in good logging statements for errors (in their code, just look for anything that starts with log(...)), so if you’re not getting a meaningful error message, it might be something unrelated to the script itself.
I’ve noticed that subtasks don’t appear to be linked to their parent task’s project. Even though the main task is part of a project, the subtasks show up in My Tasks as if they’re not associated with any project.
I’ve seen previous suggestions to remove the subtask from the main task and assign it directly to the project, but that doesn’t seem logical to me—especially when it’s clearly a subcomponent of the main task.
Is this expected behaviour or a bug? Am I doing something wrong?
Hi @Deb_Cantoni,
FYI I moved your post to an existing thread on this subject. Yes, it’s expected behavior and you’re not doing anything wrong! You can see from the discussion here that a lot of folks agree with you, and you can add your vote at the top of this thread for a change in behavior.
Hello everyone! I’m a Group PM Lead who somewhat recently has started owning Asana’s core project management functionality. As some of our Forum leaders know, this has been a mountain I committed to die on and it’s finally made it on our roadmap 
.
While we may not respond to every comment, my team reads all your posts and they are cited when we are discussing various solutions. We have a few other subtask improvements superseding subtask project inheritance, but this is in design and we look forward to being able to share more soon!
Wow that’s excellent news!! 
It’s nice to have someone on the inside committed to this topic. I’ve had so many clients and colleagues ask about this very issue over the years. The community will be so excited you’re tackling this.
Cheers to getting on the roadmap!! 
Amazing!
Tagging @Forum-team to update tags. 
All subtasks should be assigned by default to the same project(s) as the parent task. I understand that there may be occasions when someone would want it to be assigned to a different project but I would venture to say this is very much the exception and not the rule.
I encountered this when searching to try to understand why my subtasks were not appearing in my calendar view. The “workaround” was to manually go in and assign each subtask to the project (even though, again, they are simply a part of the larger task that already has a project assigned).
The very nature of the task-subtask relationship makes the necessity of a workaround a real headscratcher for me.
I’ve merged your post with an existing topic for this request.
Note especially this post from Asana letting us know that this request is in a design stage!
Agreed - Other companies does this too. And other project mgt software allows this - just not Asana.
Given we’ve kicked off foundational work for supporting this functionality, I’ve updated the status from Considered to In Development!
We’re still actively working on this big change, but I’m here to share an update that this is very much in development. My new PM @Olha_Vintonik and I have referenced this thread more times than I can count this week, so we are grateful for not only your patience, but also your detail in sharing how this impacts your workflows 
This has been a hill mountain I’ve been willing to die on the last 12 months, so I’m SO excited to see it coming to life internally!
As a new Asana user, I just encountered this issue and searched the forums for a solution. I was surprised to see that it’s by design and equally surprised to see that it’s been a request for over 8 years without resolution. Let’s gooooo..
Is this slated for a particular quarter yet?
@Jasmine_DeFoore1 this will be launching in the current quarter (that just started Feb 1)! Supporting subtasks inheriting the parent project and relevant custom fields is step one, which will then unlock other roadmap commits for the next two quarters which includes (but certainly not limited to) the ability to see all levels of subtasks within the list view (a full hierarchy tree view of parent and all levels of subtasks), support for display of subtasks on Calendar & Board views, Quick Find search / filter / sort / group by support for tasks and subtasks, and more coming. We are so excited to deliver this long awaited product functionality to you all!
HUGE set of improvements all in that one post–exciting!!
More official announcements to come, but if you’d be willing to be a part of an Early Access release, can you heart or another reaction to this post so we know to reach out to you when the time comes soon? We would love to have you all help us refine this feature ahead of a full launch (we would follow up with you before enrolling)
I just checked the winter 2026 release and this wasn’t explicitly named. Do you know if this will be rolling out in the next few weeks?
Welcome to the forum @Ilyasah_Shabazz_Davi!
I wouldn’t count on it. I think it’s hard from our perspective to grasp all of the implications of this change.
If you can hardly wait and want to be part of an early release then best give some 
to @Garrett_Knoll’s last post. 