Request: A task’s due date should be shown as the due date of the parent task, unless manually overridden.
Use Case: This is most useful for a repeating parent task. When a parent task repeats, its subtasks are recreated. If those subtasks were to have a due date or be repeating themselves, unwanted behavior would occur. The only way for the subtasks to have their due date updated would be to have it inherit from the repeating parent task.
Currently on creation of a SubTask it inherits no properties of its parents i.e Task, Project and Workspace. But I am not aware why Asana does this. It sure can’t be for flexibility, else it would be called a SubTask, instead it should be called an independent task.
But more importantly, when a subtask is added to a parent task which in turn belongs to a task, by nature it means, it is to inherit all its parents(workspace, project, parent task) behaviours, and also show in the dashboard as a respective tree. What is the reason for ASANA to deviate from this behaviour?
If the idea was to give a subtask for a task independent of all parent association it could simple a toggle button and left to the user to customize it accordingly. Besides a task inherits the parent behaviours of project and workspace, so why wouldn’t a subtask?
I agree that there should be an option somewhere for each user to define which properties of the parent task are inherited by subtasks by default. For the way I use subtasks, it would be very useful for the assignee and project to be automatically inherited. I can certainly imagine cases where the assignee would not be the same by default, but if a subtask is related to the parent task then it seems logical that it would belong to the same project in most cases. Though I often have different due dates for my subtasks, I think it is reasonable default behavior to have this inherited from the parent task as well.
When using Asana I often get assigned subtasks which obviously have a parent (with a due date). However when using My Tasks (and generally throughout the system) the visual hierarchy and layout of subtasks is really below par.
See attached screenshot. The 4 ‘no due dates’ tasks are actually sub tasks of the due date tasks but the UI here doesn’t show this at all. Why not place subtasks underneath the parent task, indented, and have a greyed out date if no specific date is set on the subtask (that takes from the parent task).
This would be so helpful to many I’m sure. This is only in the My Tasks section, they also need extra work in the kanban board and other areas IMO.
I am using the new task template quite excessively. However, what I am missing is a function to have due dates relative to the due date of the main task. E.g. Main task is due on a Tuesday, so the subtasks should be due 2 days prior to that.
This would also be useful for project templates. We are organizing events in our team, where the procedure is always the same.
@Emily_Roman I’d like to see a similar feature as @JBlumenberg and it’s indeed not the same as the request you merged it with. Is there any active thread that allows this:
Parent Taks - Due Date = “X”
Subtasks - Due Date = “X-2 days”
Formy workflow it would be very helpful, together with the feature to not plan any recurring tasks/subtasks on the weekend days. I’m trying to get more elaborate processes of construction projects into Asana.
We’ve been having a lot of trouble with recurring top level tasks and the subtasks that belong to them. We’ve noticed that when a top level task that is set as recurring is “marked complete”, the new task generates as expected, but the updated subtasks generate under the now completed task. What is the recommendation for setting up recurring tasks that have subtasks in such a way that the top level task date updates and the subtasks migrate and those due dates update as well?
When completing a recurring parent task that has subtask, the subtasks will generate under the new, incomplete parent task but the due date of the subtasks will not update automatically. This is currently an expected behaviour.
Hopefully this is something our Product team update in the future. I’ll keep you posted if any changes are made!
You basically combined the two most complex stuff in Asana at the moment: recurring tasks and subtasks If possible, try to remove the recurring from the equation by creating several tasks in advance. There are tricks to generate many identical tasks quite easily.
@Rebecca_McGrath If the top level task is set as recurring, but the subtasks aren’t, when we complete a subtask it is creating a new one under the incomplete top level task (like in the screenshot I posted) - is that expected behavior? It’s very messy because of course we’d complete subtasks before the top level task is complete, but then duplicate subtasks are now populating on the old task instead of the new.
Hi @Danae_Bowers, I can’t speak to this particular bug, but you might want to consider using a template task for this kind of thing. See Introducing templates, for Tasks! You will have to create a new task each time, but a template allows you to do so with a single click, and it avoids issues of whether subtasks are completed or not.
We have the same issue in our organization with a major monthly deliverable. I really hope this is an issue that Asana resolves. It is very frustrating and seems illogical that a recurring head task doesn’t feed into the subtask dates.