I’m creating a private project that’s part of an organizational workflow that not all contributors should have access to. Their individual contributions are not private, but others might be. The organization wants the task collaborator to be able to edit all custom fields, but I haven’t found a way to allow that with the new permission system. I set the task collaborator as a project admin, but the custom field is still grayed out. They’re able to delete the value, but not update it.
The only workaround I’ve found is to add the contributor to the project directly.
Is there another way to configure this that I might be missing?
There are a couple of things that some to my mind, could you confirm if the users are guests or members? and are the tasks where they can’t see the fields “subtasks”?
The users that were having the issue were full members. I did test with a guest and the issue persists the same. They can see the field, they can event delete the data in the field, they just can’t edit it.
This field is intended to trigger subtasks once it’s changed. The collaborator is the assignee of the task.
Hi @Christine_Bolton , I’m afraid this is expected behaviour for as long as I can remember. I don’t think it has to do with custom field permissions.
The only way for collaborators to edit fields is for them to either be part of the project or access it. Or create smaller projects (which contain just the fields you want them to edit) with just tasks that are assigned to them - that is the only workaround I know of.
The fact that the collaborators can view the field value, not being able to ‘edit’ it but actually have the ability to X (clear) the values of single-select and multi-select fields is mind boggling, something I have raised in the past with @lpb and @Bastien_Siebman but never managed to get Asana to change it (or fix it, depending on how you look at it).
And thanks for your initial reply here. @Christine_Bolton’s post definitely sounded familiar, but I didn’t have time to recreate it and I wasn’t 100% sure without doing so, until you replied–teamwork!
