Able to still set restricted field values with task templates?

I’m not able to spend time setting up the testing environment for this at the moment and realize others may have already discovered the answer. If not, others will inevitably come searching for the answer and perhaps replies to this post can help them out.

With the roll-out of the new feature to restrict fields (Jan. 2025 notes), I’m noticing this message in the screen where field restrictions are set: “This restriction applies to direct updates and new automations. Existing bundles and rules will continue to modify restricted field values.” Does anyone know if I restrict fields that are currently preset in task templates to “Project admins only,” if the editors of that space will lose the ability to use the task template? The task template presets multiple custom fields in the space. We’d ideally love to still allow the templates to be used by everyone in the space to initiate work with standardized field choices, but not allow them to change the value from the template default. I don’t see task templates addressed anywhere in the release notes or other forum posts related to field restrictions.

Hi @Elizabeth_Lumsden , I’m 99% certain that task templates are unaffected by this. An Editor can create a task from a task template, the fields will get populated but then they will not be able to change their values (only Admins will).

I can test this out for you if you want.

1 Like