Locking custom fields

Hey @Joe_Trollo and API team,

This is interesting:

Lock custom fields: You can now control who can edit custom field values across all your projects, so information is being tracked consistently, available in Enterprise.

Is there any API aspect to this? I guess I’m thinking about things like:

  • Is there a way to set this programmatically?
  • And/or is there a way to query this setting programmatically?
  • What’s the ramification if one tries to update a custom field that’s been locked for the current user? I’m guessing it’ll fail; wondering what the error code will be?

Unfortunately, the locked status can neither be set nor read through the API at this time. The only impact is that you’ll receive a 403 Forbidden response if the custom field is locked by another user and you attempt to update it.

1 Like