I have a question regarding project specified custom task field. I think I might understand it wrongly.
Let’s say I have Project A and Project B and I created a custom field in Project A then share a task created in Project A with Project B.
I expect the custom field will appear only in Project A, but NOT in Project B. But what actually happens is that I see the custom field (when seeing the task detail) in both projects.
Only when someone who is a member of Project B only see the task details, they won’t see the custom field.
If the field has been added to the library, then anyone looking at the task will see it (even if they don’t see the project hosting the field).
If the field is not part of the library, then you only see the field if you have access to the project.
Is this what you currently experience? This is expected behaviour.
Thank you for your response. Here is my setting for custom field:
I added a custom field specific only for Project A called “Project A field only”.
When a task is shared between Project A and Project B, I expect to not see the custom field when seeing the task details through Project B.
You will see the field because you can see both project A & B. If someone only sees project B, they shouldn’t see the field (that’s my current understanding)
Thanks @Bastien_Siebman … it looks like that’s how it works. So it is totally on permission basis. If I have access to both project A & B I will be able to see a custom field for a task that was set up only for Project A, for example.
I wish, it is based on which project the task details is viewed from.
Thank you for clarifying.
I think you misunderstood me. If you only have access to project B, you still see fields from project A if they are part of the library.
Seeing all the fields from all projects is in my opinion a blessing: when I am in a client project and look at an invoice, I want to see its amount and payment status. I don’t want to have to go to the invoice project to have the right “context”.
Hi @Bastien_Siebman my setting didn’t add the custom field to field library, yet it still shows in all projects.
Yes, I can see the benefit of seeing custom fields from all projects. But there are some use cases where I wish I can make custom field to appear only from the project that custom field was created.