You have to re-add the subtask to the original parent? The parent automatically picks up its Project. Are you saying entire Project disappears, Task didappears or subtask of task disappears? And what shows up in new multihomed Project? I think a little more detail may help Community determine if support issue or something else. Thanks
I’ve verified the behavior @Brooker is describing.
Steps to reproduce:
- Add a task named Task 1 as a task in Project A.
- Add a task named Task 2 as a task in Project B.
- In the detail pane for Task 1, select Move Task > Make a subtask of… Select Task 2 from the dropdown list.
Brooker’s desired behavior:
That Task 1 becomes a subtask of Task 2, but it also retains its association with Project A.
Actual behavior:
Task 1’s association with Project A is removed. You can verify this happening by looking at the activity history for Task 1; it shows “[user name] removed from Project A”.
@Brooker, this actual behavior makes sense given the design of Asana and the fact that this menu option specifically says “Move Task”. What you would need to accommodate your desired behavior is an “Add Task” option - i.e. don’t move it out of its current location but rather keep it there and also add it to a new location.
If you want this as an enhancement request, I recommend you start a new post in the Product Feedback section. You are correct that it’s a wholly different request than the one being discussed in this thread.
Is there any news regarding this feature? we have many sub-task that gets lost because they are not associated to any project. It’s very difficult and time consuming to always go over all the sub-task and making sure that they are assigned to a project. Automatic project inheritance from task to sub-task is a very important feature for us.
We get so many complaints from our users/project team when they get assigned a subtask as they cannot see what project it relates to. This is the same with the Asana APP as well. Very frustrating for users on the go and demotivating as they cannot comment or complete tasks.
We have a standard template that we use for every project - is there anyway of linking the subtasks to the parent task before we assign the subtasks out?
Please help!
Thank you
I noticed that subtasks do not automatically inherit the project tag. This is problematic when looking at “My Tasks” because it will categorize these subtasks in the no project assigned group. This post was from Aug 2017 and it seems there has been no update to fix this. Anyone know any short term solution?
Thanks
Hi @Rich_Mascalino, welcome to the Forum. Sorry for the trouble with the subtasks. You are correct, as subtasks do not inherit the Project from the parent task, the only way for them to show under a Project in your “My Tasks” list, for now, is by manually adding them to a Project.
This is a popular request in the Forum, and this feature is definitely on our radar, but we do not have a timeframe to share yet. If you don’t mind, I’m merging your post with the existing thread on this topic. Please make sure you leave your vote there. ![]()
Thanks Vanessa!
I don’t know how I didn’t find this forum post when i searched. I have been going through and assigning the subtasks to projects but it is tedious. Glad to see that it is being looked at.
We are new Asana but enjoy it very much.
Thanks again!
-Rich
No problem, Richard! I’m glad you enjoy Asana, and I understand that it can be quite inconvenient to manually add subtasks to Projects. I do hope we will be able to improve this in the near future. Have a great day! ![]()
Only the first option makes sense to me.
I would also like to throw in my vote for subtasks inheriting their parent’s project by default. It’s unclear when that wouldn’t be the case, and it sounds like a relatively easy fix to associate?
HI @Steve_Hibbs and welcome to the Forum! ![]()
We already have a thread requesting this feature so I’ve gone ahead and moved your post to this main thread to consolidate feedback and Votes. I hope it’s OK!
Hi - on the My Tasks page, when you sort by project, it shows all ‘top’ level tasks associated with the relevant project, but all the sub-tasks are shown as having ‘no project’.
How do you associate the sub-tasks (without making them ‘top’ level tasks) with the relevant project in this ‘project’ sorted view of My Tasks?
Thanks in advance!
Hi @Michael_Metis, welcome to the Community Forum! ![]()
This is a great question and we already have a thread on this topic. I have gone ahead and added your question to this thread Allow to automatically add subtasks to project to centralize feedback.
You will find all the information in the main post but please let me know if you have any questions.
Just curious, how is Asana justifying yet another price hike without this functionality? This seems to be a continuous complaint, including within my organization. For us, subtasks are useless and we aren’t able to use them since they don’t automatically link to projects.
I agree, I don’t understand why Asana continues to prioritize various “features” over basic functionality like ironing out the quirks with subtasks. Subtasks should have the same color as the project and according to this forum people have been asking for a few years now.
I agree that re-imagining subtasks is hugely important. The fix suggested here by Asana doesn’t really work. In the advanced report, I can’t see any tasks that I haven’t yet assigned a due date, and I can’t see subtasks in the timeline view. Timeline view is THE most important feature for me when organizing the 15 to 30 projects I have going all at one time. Not being able to view, move, create dependencies and filter subtasks in this view is a major flaw.
@Natalia I’m new to Asana and totally loving it. However, the fact that subtasks are not assigned to the same project automatically for me is certainly a design-flaw in the core of the system. For me this is a show-stopper to effectively use Asana for our Scrum process (where subtask creation is done continuously from parent ‘stories’)
To me it’s unthinkable that people have been requesting this basic functionality FOR YEARS and it’s not been picked up…
Could you give an estimate on when this will be implemented please?
Clearly it IS a bug or better: design flaw.
E.g. a human child of course also inherits the group/community of its parent.
Vote +1, this is extremely frustrating design. Why wouldn’t a subtask inherit the project? I can’t think of any use case where you wouldn’t expect this.
Yes it’s a design-bug.