OVERALL RATINGS
INSTALLS
255
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appHide fields, make them read-only or required, and pre-fill them by field value, work type or role. Set once, run in every space
Hide, show and require fields by condition
Show fields only where they matter and require them only when needed. Rules react to field values, work type, user or role, so each team sees a shorter, cleaner screen. No scripting required.
Set rules once, run them in every space
Manage every field rule in one place. One set of rules can span spaces, work types and views in Jira and JSM, so there is nothing to repeat per space and nothing to keep in sync across screens.
Smarter requests on the JSM customer portal
Show only relevant fields, make them required or read-only, and update field descriptions as customers fill in the request. Guide them to the right answer on the JSM customer portal.
Supporting media
More details
Field Rules lets Jira admins control how fields behave from one place. Create a rule once, choose where it runs, and it applies across company-managed and team-managed spaces in Jira and Jira Service Management. No scripting required.
🎯 Consistent data, shorter screens, less admin work.
✨ What rules can do
- Make fields required conditionally
- Make fields read-only, on screens, transitions and the customer portal
- Pre-fill values, including system fields
- Filter dropdown options and hide obsolete work types
🔁 Replace workarounds with one rule
- Show and hide fields dynamically instead of duplicating screens
- Require a field on a specific transition instead of stacking workflow validators
- Hide options instead of duplicating field contexts
- Change a field's name and description instead of duplicating custom fields
🔀 Rules react to field values, work type, user, group, space role or the transition being performed. Screens update as the user changes a value.
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
Field Rules - UI Modifications for Jira integrates with your Atlassian app
Version information
Version 3.22.0•for Jira Cloud
- Release date
- Oct 9th 2026
- Summary
- Import and export UI Modifications
- Details
9 October 2026
- Import and export UI Modifications - export any UI Modification to a file from the configuration list, and import it on the same or another Jira site. Use it to back up a configuration or to move it, for example from a sandbox or test site to production. Items that cannot be matched automatically between sites are resolved during the import. See Import and export.
18 September 2026
- Transition conditions - on the Issue Transition screen, including the JSM Agent view, rules can now react to the transition being performed. Four new conditions are available: Transition name, Transition ID, Transition destination status, and Transition destination status category. Use them to apply a rule only on a specific transition, or only when moving into a particular status or status category.
28 August 2026
- JSM Agent View support - Field Rules now runs on the agent-facing Global Issue Create, Issue View, and Issue Transition screens inside a Jira Service Management service project
- Payment model
- Paid via Atlassian
- License type
- Commercial