The rule is designed to lock the field, making it read-only. Optionally, you can override the field's description to explain why it is not editable.
On the Issue view, fields that don't have a value are automatically hidden when set to read-only. This is the Jira default behaviour when the user doesn't have permission to edit and .
Case 1. Lock the Affects Versions field in all statuses except 'Building' (right before the release). Do not apply this rule to Release Managers, who should always be able to edit the field.
