I really like the solution that was recently introduced which provided the ability to hide Custom Fields on subtasks within a Project. I believe that many would appreciate the opportunity to hide Custom Fields on task AND subtasks in the same way IF the Custom Fields pertained to another project. Through the use of multi-homing you can assign tasks to multiple projects. This then consolidates ALL the Custom Fields across those projects within the task. However, you can only view the tasks as a function of one project at a time (unless performing an Advanced Search). By that I mean, the web address to the task is different because there are separate strings for each project. I think it would be really nice to only show the Custom Fields pertain to the project in view and hiding the others by default (with the ability to show additional fields if the user chose to do so)
Thank you for sharing this feedback with us @LEGGO.
This is a great idea! And although I donāt believe we are planning to tackle this in the near future this is definitely something to consider for future updates! 
Of course, Iāll keep you posted if I have any updates on my end!
Have a great day!
Where are all my multi-homing fans at?!?!
Does nobody else feel this would create a cleaner experience yet still allow for relative data to be seen with just a click of the mouse.m?
Hi. I currently have two projects set up, but they share the same tasks. One project is a board which we use to show the progress of our deals and the other project is a list where we store data.
I currently have different fields set up in the different projects. Is there a way that when I view the task on Project A the fields from Project B are hidden and vice versa?
Hi @anon475165, thanks for reaching out!
As it stands, itās currently not possible to hide custom fields when a task is multi-homed in different projects. We already have a request for this feature here: The ability to hide Custom Fields applied to a task that don't belong to the project in which the task is being viewed so Iāve gone ahead and merged your post with the main thread to centralize feedback.
We donāt have updated yet but we will make sure to post any updates as soon as we have more information 
This is really a critical feature for anyone multi-homing tasks and using fields for automation to move tasks around between projects. It has definitely been a source of endless frustration and results in the need for lots of mental gymnastics/workarounds to keep things clean.
I really hope that āvotingā isnāt the only mechanism for getting things done at Asana as there are so many major workflow issues that should be quite simple to fix that seem to never get done. 
Lastly, Iād gently suggest that any paying customers with issues theyād like to see addressed politely contact the āsalesā department at Asana. Perhaps they will get pushed faster when an issue arises that affects customer retention and isnāt just relegated to a āfeature improvement requestā backlog coming from the community forum managers alone.
Hi,
Our team works in alot with layers in Asana where projects are included in other projects and at the end someone is asigned a task.
When the assignee receives the task it may already be connected to 2 or more projects. The result of this is that all custom fields from the other projects is showing up in the detailed view.
As information we have ābuiltā our own āMy Tasks projectā as a project in Asana since My Tasks is missing the customization that is possible in a project.
Now back to the issue, even if the assignee has chosen to hide the field from their āMy Task projectā view and cannot see it in List view, it still shows up in the detailed view if it exist in another project that is connected to the task. Could you please consider to implement that when choosing to hide (not delete) a field it does not show up in the detailed view of the task. What i see as a importent field depending of my work may not be as important for another one to see.
Thank,
Thanks for sharing your feedback with us, @Patrik_Haasz! We already have a thread on this topic so Iāve gone ahead and merged your post with The ability to hide Custom Fields applied to a task that don't belong to the project in which the task is being viewed to consolidate feedback!
I layout critical information in custom fields such as contract values and such. It would certainly be nice to hide custom fields when information should not be divulged to the assigneeās.
I have voted as well but certainly hope Asana can move on this feature quickly.
Iāve already upvoted but wanted to keep this top of mind as Asana plans future roadmap items. This is a critical feature as we continue to roll out Asana and expand across our org. We currently have tasks multi-homed across several projects for visibility to all Global teams. The loooooooonnng list of custom fields on the task is distracting and causes confusion. Taking away from the overall efficiency and effectiveness that Asana provides. Would love to see this feature sooner rather than later!
This would be amazing! I really hope you introduce this feature at some point. We are really struggling with all the custom fields being shown to everyone when the task lives in many projects.
We highly request a feature where parts of the info in the card can be hidden from some users. Our use case is customers collaborating with us as an agency. Some parts are connected to a task we donāt want them to see, for internal eyes only. The current solution is to have a connected card on a board the customer canāt access. This is not a feasible way of working for us.
Thanks in advance!
Hi, I wanted to check in and get an update on the status of this feature roll-out. Custom fields are becoming more robust and integral throughout many userās workspaces. The ability to hide sensitive information (like pricing and budgets) is a āmust haveā at this point.
Is this still in the works?
Chiming in here with the same questions! Any update on this now that weāre in 2024? (Looks like itās been 4 years since originally requested?)
My organization is about a year into our adoption of Asana, and while multi-homing a task is a great feature, itās getting difficult to use task fields effectively because thereās so much clutter on tasks that live in 3 or 4+ projects.
Thanks!
Hi, is there any update on this feature? āAbility to set visibility of custom field based on the projectās section OR by logged-in userā
This feature would add a lot of value to our organization, and help facilitate migrating users from other products (i.e. Jira ā Asana).
I wanted to check in again on the status of this potential update.
Thanks,
We also need this feature to be functional, as it stands itās hard to get engagement with asana org wide because of our overlapping boards. This creates a lot of churn for users that have to sift through countless fields, but we also need the tasks to talk to the other board. Is there any solution being created?
Voted and am surprised this has been requested for so long without some sort of movement.
My team would also benefit from this feature. Trying to figure out a workaround as we speakā¦