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 at that.
Point being, the aforementioned value appears greyed out, prompting that this is ‘read-only’, i.e. I cannot change this value, which makes sense…
BUT the only thing I can ‘change’ is to clear the value of that custom field. Why is that?
For years I have been trying to understand the logic and use cases behind this ability but with no real luck. It has since become a problem on numerous occasions, with users (including myself!) accidentally clearing values of fields that they should not, and theoretically do not, have access to.
My suggestion is to disable this ability from users doing so, i.e. remove the ‘X’ upon hover.
Unless I’m missing a use case that this would actually be preferable…?
It could perhaps be an additional option in the custom field’s ‘Edit field’ settings, which becomes available to checkmark, once the field is added to the library.
Additionally, the tool tip mentions ‘delete the field…’ from the task but that is misleading. It will not delete/remove the custom field from the private project B when I click the X, it will just clear the value. I understand that is a mouthful for a tool tip but…
My client has a private project with the set of custom fields added to the library. He wants to assign tasks from this projekt to the man that is not member of this project. This person sees the task on his My Tasks list, he sees the custom fields value but cannot edit it. He can only remove it (then the custom field disapear from the task. Is it expected behaviour or bug?
I reproduced it in my Asana. Here the project with example custom fields CS A, CS B and CS C:
Hi @AnnaPapiernik , I’m assuming these fields belong to the custom field library so that person could theoretically add those fields to their My Tasks (if they are NOT a Guest) BUT that is not at all ideal because these fields would apply to ALL their tasks in My Tasks.
The obvious way this person would be able to edit these fields is to either add the person to the project or make the project public. But this will not work for your client’s case.
Therefore, the best way is to create another project just for this person (and your client), add just the fields from the library that your client wants the person to edit and then multihome only the relevant tasks that apply to them. This could be automated with a rule that adds the tasks, that the person is assigned to, into this new project.