Any movement on this? Ideally custom fields could have an yes or no option as to whether subtasks will inherit that field from their parent task. Or all subtasks inherit the parent tasks custom fields but if you need to you can manually change it. My department uses subtasks and this would save a lot of time.
8 Likes
Is there a way to make the subtasks automatically inherit the main task’s Priority?
I currently have rules that automatically create subtasks, but I can’t find a way to have the Priority trickle down to subtasks once it’s (Priority) selected on the main task.
*I do not have Flowsana
12 Likes
Mimicking @Charissa_Bass’s sentiment since it has been a while. Any movement on the ability to copy parent task field values to the corresponding subtask field values? This would be immensely helpful.
5 Likes
Its always the same.
Asana has some nice features, but when it comes to use them, there is always a last puzzle-peace missing.
So much wasted potential…
2 Likes
Would also love to know if there is a way to do this without flowsana, since first posted?
1 Like
Hey!
I have a question regarding the work around.
When I multi select tasks and change a fiels for all, it doesn’t change it for the subtasks as well, unless I expand all tasks and then multi select them.
Is there a way to select all tasks and also the sub tasks in them wand change a field to all at once?
Thany you,
Oren
Welcome, @anon16431528,
That’s the intended behavior.
Yes, that’s what’s shown in the screenshot above. If you’re not able to replicate that in your environment, include a screenshot to show us what you’re experiencing.
Thanks,
Larry
1 Like
Hi Phil, the “read about here” link goes to a 404 page. Can you please send a new link?
Link updated! (Here is the new one.)
1 Like
I am also looking to inherit a custom field on a subtask utilizing a single-select. Is there any movement?
10 Likes
Would love to see this functionality! Is this in the Asana development roadmap?
Hi @Nicholas_Cusick,
Asana doesn’t publish a public roadmap, so we just have to wait and see if it’s something they announce as coming at some point.
When running a rule to create tasks or subtasks from a task, it would be great, if there would be a feature to inherit chosen custom fields from the trigger task the same way as it can be done for name, due date or assignee. Something like that:
That way you could choose which fields to inherit from trigger task by rule.
Peter
2 Likes
Hi @Peter_san ,
I’ve merged your request with this existing one. You didn’t vote for your own topic, so no votes were transferred. You can vote for it at the top.
“Global custom fields” would be so important.
They would open up countless possibilities if sub-tasks and parent tasks could synchronize with each other regarding such specifically selected custom fields.
This way, rules in the sub-task could also be triggered via the parent task.
How do I know this?
We implemented exactly this in Make and would love to do without Make in the future. I would also consider this a huge enrichment for the community and the software.
This is doable now, at least when creating new subtasks through custom rules. Not sure when the feature showed up but you can select the parent custom field value when using a rule to create a subtask.
3 Likes
@JeremieBergeron I have created a “When Rule is run manually” rule that creates subtasks with the inherited values on demand. Very useful!
@Forum-team, Is the functionality in the last two posts new, A/B, or did I miss it? Is there an announcement? I see this which seems new:
Thanks,
Larry
3 Likes
This feature is awesome, just what our team was looking for! However, it only gets us half way there. This new feature enables for inherited fields for new subtask creation, but we’re also hoping to see (one day) the ability to create a workflow whereby inherited subtask custom fields are updated based on updated parent custom fields.
Why is this an issue? Because when you create a new parent task, you do not have enough time to enter custom fields before the workflow automatically creates subtasks (that is, if you have the workflow set up such that subtasks are created automatically upon parent task creation). The only way around this, it appears, is if you set up the workflow automation such that the workflow is triggered only upon manual trigger. And no luck if you are hoping to see automatic update of subtask custom fields once the parent task (and subtasks) are already created.
Wondering if anyone on the Asana development team could address whether this additional feature is being considered?
All that being said, a big kudos to Asana! Definitely an improvement over having to use 3rd party tools that you have to pay for separately.
2 Likes
@Nicholas_Cusick we’re successfully using Flowsana’s Variable Substitution rules to update the custom fields of subtasks that belong to a parent task. Here’s a link Variable Substitution in Flowsana that describes it.
1 Like