Hi,
I don’t think so, the only way to see it is to have the subtask belong to the project (multi-homing the subtask into its parent project, possibly stored inside a closed section at the bottom of the project).
Hope that helps.
1 Like
It would be really helpful if the inherited fields could be shown by default on subtasks. Multi-homing per @Bastien_Siebman suggestion above does work, but 1) it creates clutter by having to house all subtasks out on the parent project, and more importantly 2) it requires a savvy user to take a couple of extra tedious steps to properly organize and is not quick or intuitive.
Being able to set up subtask templates would also be very helpful and would facilitate default display of custom fields.
1 Like
It could be made almost frictionless by hosting subtasks in a dedicated section at the bottom of the project + making it automatic through automation. But I agree this might not be acceptable for everyone, this would still be considered a workaround.
I wish we could do this - I have searched this forum for help on this issue multiple times, I’m not sure why Asana won’t let us treat subtasks as first class work
1 Like
This is not that easy. A lot of people do not want what you want and want to keep subtasks the way they are.
Until/if Asana offers a setting for this, see my partial workaround tip here:
Larry
1 Like
The subtasks inherits the fields but they are empty. is there any way to have the subtask inherit the values from the parent task rather than an empty field?
1 Like
Not yet, this is expected behaviour for now.
This is exactly why the setting should exist.
Sure, leave subtasks as they are for those who don’t care. But for those of us who are wasting precious time by clicking ‘Show inherited fields’ on every single subtask, we should be able to show them by default.
7 Likes
You would think they would implement a simple fix for this since there are people who have been asking since 2021…LOL.
2 Likes
Hello, guys.
Any suggestion when important features will be implemented?
It is a good strategy to release new features like recently “Notes” but maybe it is a good tactics to implement some minor features which make life easy? I am sure that this can be implemented not more than few days.
3 Likes
Popping in to say this is also a very annoying problem for my team, we are just getting set up in Asana and we’re mainly using subtasks, so clicking ‘Show inherited fields’ all the time to view details is not ideal
2 Likes
I also want Asana to fix this!
Asana please add this as a feature update! My team is missing valuable information and having to click on “Show inherited fields” is adding an additional step that wastes time.
3 Likes
Is there a way to manually change the default visibility of inherited fields/custom fields when you view a subtask in Asana to always show instead of keeping those hidden?
It would save me an extra CTA click when I want to update the inherited custom field for subtasks.
If there exists a solution already, would love to know! Thanks in advance!
I’ve merged your post into an existing topic where you can click the title to scroll to the top and vote by clicking the Vote button.
Thanks,
Larry
Thanks!
Really amazed that this thread is open since 2020 and the users have NOT been provided with a setting option in the last 5 years to make inherited fields’ visibility changes according to their needs, damn! Any workarounds, fellow subtask lovers?
In projects’ list views, you can expand to show subtasks (to the first level) and fill in any values for which you’ve configured columns to appear.
Also, back to the task detail pane, if you have a shared custom field added to your My Tasks custom fields, then it will be open by default for you without the extra click.
1 Like
You mentioned somewhere on this thread that half of the customers prefer this feature to be hidden by default, which is understandable. However, that also means the other half may prefer it visible (even if it’s just 20%, since 5 years have passed now, it’s still a big chunk). I believe that instead of enforcing a default for everyone, giving users the option to toggle this setting based on their personal preference should be the way forward. Just my personal thoughts to keep this thread alive!
Additionally, I feel that some of your responses on this thread come across as dismissive of the community’s feedback. You may have strong data to back your responses but being more empathetic to user’s needs in your responses could not be that bad.
Thanks! Will try it out!
1 Like