Field Rules - UI Modifications for Jira
  • About Field Rules - UI Modifications for Jira
  • Rules
    • Enable Self-Assignment Only
    • Hide field options
    • Hide issue types
    • Lock field
    • Make field required
    • Pre-fill field
    • Show field
  • Jira Administrator
    • Setup guide
    • Security
    • Limitations
  • Support
    • Service Desk
  • Atlassian Marketplace
    • Forgappify apps
Powered by GitBook
On this page
  • UI modification
  • Contexts
  • Rules
  • Adding a New Field Rule:
  • Managing Rule Dependencies and Execution Order
  1. Jira Administrator

Setup guide

PreviousShow fieldNextSecurity

Last updated 9 days ago

Follow the steps to get started:

  1. Install the app - you will find us on the .

  2. New item Field Rules - UI modifications will appear in the Apps section of the left navigation of Jira admin settings.

  3. Create your first UI modification

UI modification

A UI Modification (UIM) is an entry that allows you to define:

  1. Where the issue UI should be modified - Contexts

  2. How it should be modified - Field Rules

  3. What it does - Name and Description

All these elements together form a recipe for how a specific issue view should behave in selected projects and under certain conditions.

Contexts

A single context is a combination of a project, issue type, and view type. UIM support for different view types depends on a project type, learn more what is currently possible in the Limitations section.

View types currently supported by the app are:

  • Global Issue Create

  • Issue View

  • Issue Transition

Rules

Rule type
Global Issue Create
Issue View
Issue Transition

Adding a New Field Rule:

  1. Click on the Add Rule button.

  2. Select a rule type from the options on the left.

  3. Choose the field that will be modified.

  4. Configure the rule by selecting the desired preconditions.

  5. Save the rule to apply the changes.

Managing Rule Dependencies and Execution Order

All UI Modifications (UIMs) defined in the app are executed in parallel to ensure better performance. However, this can lead to race conditions if one UIM depends on fields being modified by another. In such cases, the behaviour may be unpredictable.

To avoid these conflicts, we recommend that all rules depending on the same fields be placed within a single UIM. Inside a single UIM, rules are executed sequentially, ensuring that dependencies are respected and execution order is maintained.

This approach helps guarantee consistent behavior and avoids unexpected results due to timing issues between parallel executions.

Due to API limitations, some rules are designed to work only for certain view types. We are actively developing new rule types and welcome your feedback and ideas. Feel free to reach out to us through our .

support portal
Enable Self-Assignment Only
Hide field options
Hide issue types
Lock field
Make field required
Pre-fill field
Show field
Atlassian Marketplace
Administrative interface after app installation, where UI Modifications can be created and managed.
Example 1. UIM configuration example
Example 2. Adding a new rule
Jira UI showing Create UI Modification admin page for configuring field behaviours like show field, hide field, make field required, and conditional fields for dynamic forms
Jira field behaviour configuration for Global issue create view using Enable Self-assignment Only rule with preconditions based on user groups and project roles
Jira field behavior example using Make Field Required rule with dynamic form preconditions based on priority field, user groups, project roles, or individual users