I’m excited to announce we just expanded edit restrictions to support Assignee and Due Date fields. This means you can now apply the same level of control to these core fields as you can with custom fields, limiting who can update task assignments and due dates to reduce accidental changes and improve governance.
Whit this update you can:
Prevent unauthorized changes to critical task information
Limit who can modify assignments and deadlines
Same restriction capabilities across all field types
This update also directly addresses feedback from our community! Thank you to everyone who shared their needs in these Forum threads:
Great update! Locking assignee and due date fields will definitely boost accountability and prevent unwanted changes. Curious how teams plan to use this in daily workflow.
Fantastic addition. You want teams to have freedom to manage projects but locking down key dates is essential. You don’t want those moving without discussion and particularly after you have updated sponsors and stakeholders.
Sorry, @JenDavis, there isn’t, I’m afraid. You can usually see the old version prior to the change at the bottom of the task detail pane in the audit trail if you are in the All activity (not "Comments) tab.
Is there a good explainer or visual for how field restrictions work when a task is multi-homed? We are just beginning to try some field restrictions but are hesitant and struggling to find answers within the official articles or community forum. We just verified task templates can still be utilized by Editors even if restricted fields are prefilled. Questions that have come up around our multi-homed tasks:
If a person is made an Editor by any permission setting of any project where the task resides, are they now considered Editor role in a project where field restrictions are set to Project Admin and Editor, or do they need to explicitly be made an Editor in that project where the restrictions are in place in order for that project’s field restrictions to apply to them?
Editor in project 1, which restricts fields A, B, and C to project admins & editors
Commenter in project 2, which restricts fields D and E to project admins and editors
Able to edit D and E because Editor in project 1?
Not able to edit D and E because not named an Editor in this project?
If an Editor in one space has field restrictions preventing a specific field, but they are Project Admin in another board where the task exists, is that restriction lifted and they now have full access to edit the field?
Editor in project 1, which restricts fields A, B, and C to project admins only
Project Admin in project 2… access to A, B, and C?
Prevent unauthorized changes to critical task information
Limit who can modify assignments and deadlines
Same restriction capabilities across all field types
