About Field Rules - UI Modifications for Jira
Field rules are ready-to-use, simple instructions that tell Jira how to modify issue views in specific contexts and under certain conditions. Currently, Global Issue Create (GIC) and Issue View are supported.
A list of field rules is called a UI modification (UIM). It is created by a Jira administrator for specific projects, issue types, and supported view types.
A single Field rule targets a specific field and allows you to modify its behaviour consistently for a selected UIM context. For example, you can choose to always hide outdated issue type options or make a field required in the Global Issue Create view.
One of the standout features of the app is the ability to set optional preconditions, allowing you to apply rules only under specific conditions. This flexibility enables powerful customizations, such as restricting the visibility of certain issue types for designated user groups or making fields required based on the values of other fields. With preconditions, you can fine-tune how and when your rules are applied, ensuring your workflows adapt to your unique needs.
Provided Rules
Built in Forge
The app is developed using Atlassian's Forge platform, ensuring secure and seamless integration with Jira’s infrastructure.
UI customisation is made possible through a low-level API called UI Modifications (UIM), available exclusively for Forge apps. The number of supported operations and fields depends on the view types supported by the API provided by Jira. Read more about what is possible in the Limitations section.
Use cases
Here are some powerful use cases that showcase the flexibility and control the app provides:
Multilevel selection: Guide users through cascading field selections, dynamically revealing necessary fields and options as they make choices, which simplifies complex workflows.
Allow only self-assignment: Enforce assignment policies, ensuring users can only assign tasks to themselves.
Conditional fields: Reveal the 'Please explain' field conditionally based on user choices and make it required.
Editable fields in specific statuses: Make the Affects Version field editable only when issues are in specific statuses, while still allowing release managers to make edits as needed.
Conditionally make fields required based on the values of other fields, ensuring that users provide all necessary information while avoiding an overload of irrelevant inputs.
Hide obsolete options: Clean up your interface by hiding outdated issue types or irrelevant checkboxes based on user selections.
Contextual priority options: Dynamically display different priority options depending on the issue type, improving decision-making.
Field options tailored to priority: Narrow down field options based on the selected priority, keeping your workflow focused and efficient.
Get started
You will find the app on the Atlassian Marketplace. Follow our Setup guide to get started!
Last updated
