Limit Project Custom Field visibility so it's only visible to the project members (not collaborators)

English Forum Tips and Tricks
1

Hey!

I thought that Custom Fields, when added to specific projects, would only be visible to members of that project. However, it seems other members can view it as well if they are added to the task as an assignee.

How can I make a custom field only visible to the users that are in the project it is added to?

Scenario:

  1. Create a custom field called “Price”, and add it to the project “Client project”. This project only has one member, “Client user”.

  2. Create a task in the “Client project”, and enter “100” in the “Price” field

  3. Add the task to a second project, called “Developer tasks”. This project only has one member, “Developer user”.

From what I have seen, “Developer user” is fully able to see the “Price” custom field and it’s value, even though that custom field has not been added to the “Developer tasks” project.

How can I solve this?

Do I seriously have to create a separate, duplicate task and then keep both tasks manually in sync when anything else changes?

2

An option is to create a subtask and multi home that subtask to the developer project. (shortcut: [tab]+[p]) The subtask may inherit the fields, but not the field values.

Another option is to be transparant about the price.

1 Like
3

Thanks for the tip about subtask multi-homing, I wasn’t aware of this. I did notice some weird behaviour where field values aren’t available to the subtask unless the parent task is assigned to the same person as the subtask.

Unfortunately, creating a subtask doesn’t help since I then have to duplicate the same information to the subtask and manually keep them in sync, among many other issues with this approach. The same problem applies if I make a totally separate task and just add a link to it.

With a task system like Asana, the goal is to avoid this kind of duplication and manual syncing work, so I’m quite frustrated with the lack of flexibility here.

Being transparent with the Price works in some cases but not others, and “Price” is just one example of many. There are definite common use cases where custom fields absolutely can’t be viewed by certain people and I don’t think that’s a big ask for a tool like Asana to cater for.

I did ask their support team, but no reply for over a week now!

2 Likes
4

I would suggest adding your vote and voice in this topic, as it looks like implementing this would solve your problem:

1 Like