Bug in permissions

[lpb]

@Marie, @Jandieg, @Juan_Diego,

I believe this is the expected behavior, not a bug.

For an explanation, see:

Prevent users to edit Custom Fields nested in Projects they don't have access to (multi-homed Tasks)

Thank you all for your patience! I’ve worked closely with our support and dev team to investigate this behavior and I can confirm this is not a bug or the result of a recent change; this is in fact how custom fields in multi-homed tasks have behaved since their original launch; but let me give you more context to understand why this is happening: In our guide article dedicated to custom fields, we mention that “Anyone with access to a task can modify the values of its custom fields.” This is b…

For workarounds, see:

Prevent users to edit Custom Fields nested in Projects they don't have access to (multi-homed Tasks)

Custom field values, like anything else in the task, is visible if the task is visible. I too wish there was a way to have some task information project-related and visible only if you have visibility into that project, but nothing like that exists. They are hacks but two workarounds exist: One would be to add a link to a task in a private (to some) project as I mentioned here: That link will appear as Private Link to those w/o access. For the rest, it could contain the set of “private” cu…

Perhaps this thread should either be merged, or re-created as a product feedback votable request?

Thanks,

Larry