Ability to "lock" a custom field, so no user can edit it

Some of our fields in Aha are solely dictated by the field in Jira, for example Status.

Statuses in Jira have validations, which cannot be recreated in Aha. If we map Status bi-directionally, we run into errors because Aha is trying to overwrite a status from Aha into Jira, but the validation may not have been met in Jira

Similarly, if we do a One Way integration, when someone updates the status of a record in Aha, then it is automatically out of sync with Jira. 

A potential solution to this is to prevent a user from being able to update the status field in Aha. Essentially locking the field, so that it is only ever updated by the status in Jira.