Custom fields showing to client. How to hide them?

[Magasul]

I made a project for internal use (with fields like budget and profit) and a twin project for the client that doesn’t have these custom fields. Yet, when I add a task to both projects, the client can still see budget and profit.
These fields are removed from their project, yet, when they open the task, they can see the fields and their values. How do I make sure that it’s not visible to them?

[lpb]

@Magasul,

The solution is to make the custom fields local to your private project:

More tools to organize owned tasks -private tags field?

@anon62246207, As a partial workaround, until/if all that functionality is added by Asana (probably not anytime soon)… If you’re on a paid Asana plan, you can use local (not org-wide) custom fields for private data on your tasks. Make a private project with all the private custom fields you want to use on any task, then multi-home any tasks that you’d like to specify private data on to this private project. You will be able to see the custom fields and values but no one else will. Larry

But beware:

Task Details > Remove the ability to delete the value of a custom field (in the library) that is in a private project

Scenario: I am a member of Project A and can see Task X inside it. Task X is also multi-homed into Project B which is private - I have no access to it. Project B has a custom field which is part of the org’s library. In task X’s Details pane, I can see that custom field’s value greyed out (because it is in the org’s library and in a project that I don’t have access to). Whether I should see this custom field’s value or not is another debate, but it is the expected behaviour so let’s leave it …

Thanks,

Larry

[Magasul]

And yes, these are custom fields added to the library, because it has formulas and I don’t want to re-create them each time.

[Magasul]

Yes, but I have these fields as custom formula fields and I don’t want to recreate them each time I create a new project.

[lpb]

Yes, @Magasul, it would be nice if a solution existed that didn’t have that unfortunate consequence. I’ve passed along this request to a contact in Asana product management.

Thanks,

Larry

[Magasul]

I’ve come to the conclusion that Asana is… bad… How can a feature this basic not exist? We’re switching to something else… bleh…