Lock Field

Applies or removes a field edit/view lock on a ticket. Leave the Field input unconnected to lock every field.

Inputs

• Ticketrequired — Ticket. Selects the ticket whose field lock is changed.
• Field — Field. Selects the field scope to protect, and leaving it disconnected applies the lock to all fields of the chosen kind. The executor reads the field id from the resolved field value when present, so a connected field narrows the lock to that specific field.
• Locked — Boolean. Overrides whether the field lock is applied or removed. When true, the node creates the lock; when false, it removes matching active locks.
• Exception Users — List<User>. Lists users who are allowed to bypass the field lock. The executor resolves each connected user to an id and stores those ids on the lock.

Outputs

• Signal — Boolean. Indicates the field lock was applied, removed, or already absent and downstream execution may continue.

Configuration

• Mode — Select (Edit, View). Chooses whether the lock blocks edits or view access, and the executor maps it to the edit or view lock type. Edit locks prevent changing the field value, while view locks prevent reading the field value.
• Locked — Boolean. Sets the default locked state when the input is not connected. When true, the node applies the lock; when false, it removes matching locks instead.
• Clear All Locks Of This Type — Boolean. Removes every active lock of this type on the ticket instead of only the matching scoped lock. Use it when you want to release all field locks for the selected mode regardless of field scope.
• Reason — Text. Stores the text written onto the created lock and becomes the release audit context when the lock is removed later.

Example use cases

Freeze on Done

When a ticket reaches Done, lock all fields so closed work cannot be silently edited.

Protect one field

Connect a single Field and add Exception Users so only leads can change the priority.

See also

• Type Reference
• All nodes