OVERALL RATINGS
INSTALLS
1
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appLock the Jira fields that matter so only the right people can change them, and put back edits that slip through
Locks that hold
Read-only on the create, view and transition screens. Changes made any other way (bulk edit, list view, the API, imports, automation) are put back within seconds and logged.
Lock when it matters, for whom it matters
Always, in chosen statuses, during an active sprint or while a JQL filter matches. Exempt people, groups and project roles, or lock only certain values, such as Highest priority.
Nobody is left guessing
When a change is put back, Fermata comments on the work item, mentions the person and names who can make the change. An issue panel shows what is locked and why.
Supporting media
More details
Some Jira fields should not change once a decision is made: the estimate after sprint planning, the priority a manager set, the contract value finance approved, the fix version on work that is Done. Jira lets anyone who can edit a work item change all of them. Fermata locks the fields you already have, without replacing them with new field types.
A rule picks fields, projects and issue types, when the lock applies (always, in chosen statuses, during an active sprint or while a JQL filter matches) and who can still change them: people, groups or project roles. Locked fields are read-only on the create, view and transition screens. Changes that arrive another way, through bulk edit, the list view, the API, imports or automation, are put back within seconds, logged, and explained in a comment on the work item.
Try any rule in audit-only mode first. Fermata acts only on what a Jira administrator configures. Zero external network egress.
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Fermata: Field Locking for Jira integrates with your Atlassian app
Version information
Version 3.2.0•for Jira Cloud
- Release date
- Sep 25th 2026
- Summary
- Lock the fields that matter, and put back changes that slip through
- Details
First Marketplace release.
- Lock native fields by project and issue type: always, in chosen statuses, during an active sprint, or while a JQL filter matches
- Exempt people, groups and project roles; optionally let automation and apps edit
- Lock only certain values, such as Highest priority
- Changes made outside the screens are put back and logged, with an explanation comment
- Values set when work items are created (including imports) are reset to the default
- Audit-only mode, rule templates, an issue panel showing what is locked
- Activity log with filters and CSV export
- Payment model
- Paid via Atlassian
- License type
- Commercial