Good idéa, but not in it’s current form
The idea is great, but please revert this change ASAP in it’s present form, our production is screwed up, or make it optional make so that we can choose which fields to be displayed so that I can remove them myself.
The general idea of having fields from the parent task in subtasks is a good one, but what I interpret from the previous forums posts is that the value’s of those fields should be shared – so that it can be updated both from the parent and from the subtask? That would be a good feature (espacially in task-sub-sub-sub, more levels), but in the way it’s built presently it doesn’t really do anything new that you couldn’t to with some creative thinking before this update anyway.
How to do the same thing in Asana before the update
The example above is our main task. It’s got a custom field called “Account Name” and as you see the project is named TESTING. Note that the value in the “Account Name” field is “CUSTOMER A”.
I also have a subtask in this “Parent task in project” named “Subtask”. In the subtask there is the same field “Account Name” from your update, but it has no connection to the field in the parent task, and I can write any value here, in my example “CUSTOMER B”. This just makes the users unsure of where to update the field and they write things in the wrong places. If the field value would come from the parent task, it would make sense, already showing “CUSTOMER A”, but instead now I just have another field with the same name.
If I would want this functionality I would (to add the same field name in both parent and subtask), I would simply add another project, say “TESTING 2” add the custom fields to that project (I can’t add “Account Name” since it already exists now from your update, but I added “Account Name 2” instead for this example). I would just then add the “Subtask” task to that new project too (so that it is in both projects) making it inherit the fields from the new project, giving me “Account Name” on both parent and subtask with two values as you have done in your latest update.
If I could however update the field from both the parent or the subtask, making the field shared this would be a good feature, but in it’s present form it doesn’t make any sense for me.