FieldLock for Jira is for finance, PMO and operations teams who keep figures such as contract value, budget or cost estimate in Jira Cloud issues and need to know nobody overwrote them quietly.
Locked mode uses a FieldLock number field that refuses edits in the issue view, REST API, bulk edit and automation. Guarded mode keeps an existing field, with no data migration: once a value is approved, outside changes are reverted, usually within a minute or two; until then the field accepts its first value.
Changes go through a request with a reason, decided by the project admin or a project role; an optional four-eyes rule blocks self-approval of requests. Approvers may also set a value directly, which is logged. The history is a tamper-evident log (SHA-256 chain) you can export for an audit.
FieldLock does not hide fields, does not support date fields and has no bulk import into Locked fields. It runs on Atlassian Forge and is published by Aphex Coding.
