Control Jira field behavior without changing screen configuration
Hide, lock or require fields by user, group, role, issue type, project and screen so teams see only what matters.
Field Visibility Rules
Hide fields from specific users, groups, roles, issue types or projects without maintaining separate screen schemes. This helps teams reduce clutter and simplify issue creation and editing.
- Hide fields by role, group or named scope
- Apply rules per project or across all projects
- Support create, edit or combined screen targeting
Read-Only and Required Enforcement
Mark fields as read only or required based on context. Teams can protect sensitive values from edits while improving data quality at the point of entry.
- Read-only field controls without workflow hacks
- Required field enforcement at entry time
- Stronger governance for operational teams
Granular Scope Across Jira Contexts
Field Governance is designed for administrators who need precise control across users, groups, roles, projects and issue types. It centralizes field-behavior rules so teams can scale Jira with less administrative friction.
- Issue-type and project-specific rule targeting
- Scope for everyone, named users, groups and roles
- Cleaner governance without duplicating screen setups
More Details
Field Governance helps Jira administrators control exactly what users can see, edit or must complete across issue forms, without relying on multiple screen configurations.
It is particularly valuable for teams managing complex Jira setups where field behavior needs to vary by project, issue type or user responsibility while keeping administration maintainable.
Placeholder screenshots and documentation links can be replaced as soon as final product assets are available.