> For the complete documentation index, see [llms.txt](https://docs.forgappify.com/field-rules/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.forgappify.com/field-rules/jira-administrator/limitations.md).

# Limitations

Supported spaces, views and entry points, and how Field Rules behaves alongside other UI Modifications apps.

**Field Rules - UI Modifications for Jira** is built on Atlassian’s **Forge platform** and uses the **UI Modifications (UIM) API**. Because of this, the app’s capabilities are closely tied to what the underlying platform supports.

This page covers:

* The spaces, views and entry points where UI modifications run.
* The fields available on each view.
* How the app behaves alongside other UI Modifications apps.

## Supported spaces and views

UIM support depends on the space type and the view. Read full details in the Atlassian documentation:

* [Jira views](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-ui-modifications/#view-specific-requirements-and-limitations) - Global Issue Create, Issue View and Issue Transition
* [Jira Service Management views](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-service-management-ui-modifications/#view-specific-requirements-and-limitations) - JSM Request Create and JSM Agent View

### Global Issue Create

UIM for Global Issue Create (GIC) currently supports the following space types:

* Company-managed and team-managed Jira Software
* Company-managed and team-managed Jira Work Management

#### Supported entry points <a href="#supported-entry-points" id="supported-entry-points"></a>

The Global Issue Create (GIC) modal can be opened from several places. These entry points are supported:

* The global **Create** button in the top **Navigation bar**
* The `c` keyboard shortcut
* The work item view **Add a child work item** and **Create subtask** buttons
* A Forge app with custom UI using `CreateIssueModal` from `@forge/jira-bridge`

*The GIC modal with UIM only opens from **Add a child work item** and **Create subtask** if the summary and at least one other field are set as mandatory for the work type.*

{% hint style="warning" %}
The **Create linked work item** entry point is not supported.
{% endhint %}

### Issue View

UIM for Issue View supports the following space types:

* Company-managed and team-managed Jira Software

#### Supported entry points <a href="#supported-entry-points-1" id="supported-entry-points-1"></a>

Issue View can be displayed in several places in Jira. These entry points are supported:

* Full page work item view
* Board work item view
* Backlog work item view
* List work item view
* **Issues** page work item view
* Search work item view (global search)
* A Forge app with custom UI using `ViewIssueModal` from `@forge/jira-bridge`

### Issue Transition

UI modifications only run on the **new experience** of the Issue Transition dialog. The legacy dialog isn’t and won’t be supported. UIM for Issue Transition supports the following space types:

* Company-managed Jira Software

Transitions in Jira Service Management spaces are covered under [JSM Agent View](#jsm-agent-view).

#### Supported entry points

The Issue Transition dialog can be opened from several places. These entry points are supported:

* Full page work item view - changing the work item status
* Full page work item view - running **edit status** from the command palette
* **All issues** page - changing the work item status
* **Project** > **Backlog** - changing the work item status
* **Plans** > **Timeline** - changing the work item status
* **Active sprints** - moving a card between columns
* **Active sprints** - changing the work item status from the work item dialog

### JSM Request Create

UIM for JSM Request Create runs on the customer portal's request form, for both company-managed and team-managed Jira Service Management spaces.

#### Supported entry points

* Portal **Request create** form

{% hint style="warning" %}
JSM Request Create is not supported for embedded request create forms.
{% endhint %}

Field support on the portal is more limited than on the Jira views, see [Supported Fields per View](/field-rules/jira-administrator/supported-fields-per-view.md#jsm-request-create-notes) for the details.

### JSM Agent View

UIM for JSM Agent View runs on the agent-facing Global Issue Create, Issue View and Issue Transition screens inside a Jira Service Management space. All three Agent views work in both company-managed and team-managed Jira Service Management spaces.

Only spaces of type Jira Service Management are offered when configuring this context.

Field and rule support on each Agent view mirrors the corresponding standard Jira view - see [Supported Fields per View](/field-rules/jira-administrator/supported-fields-per-view.md#jsm-agent-view-notes) for details.

#### Supported entry points - Global Issue Create (Agent view)

* The global **Create** button in the top **Navigation bar**
* The `c` keyboard shortcut
* The work item view **Add a child work item** and **Create subtask** buttons
* A Forge app with custom UI using `CreateIssueModal` from `@forge/jira-bridge`

#### Supported entry points - Issue View (Agent view)

* Full page work item view
* Queues work item view
* Reports work item view
* Board and backlog work item view
* List work item view
* Search work item view (global search) and the detail view of the work item navigator
* A Forge app with custom UI using `ViewIssueModal` from `@forge/jira-bridge`

#### Supported entry points - Issue Transition (Agent view)

* The transition screen opened from the work item view
* The transition screen opened from a board card

{% hint style="info" %}
**Request create form fields on Issue View (Agent view).** Atlassian does not apply UI modifications to fields that are part of the request create form on Issue View (Agent view).
{% endhint %}

### Customer Service Management

[Customer Service Management](https://www.atlassian.com/software/customer-service-management) (CSM) is a separate Atlassian product built on its own set of Forge modules, distinct from the Jira and Jira Service Management UI Modifications module that Field Rules is built on.

UI Modifications are not supported on Customer Service Management spaces, so Field Rules cannot run there, on either the Agent view or the Customer view.

## Supported fields per view <a href="#supported-fields-per-view" id="supported-fields-per-view"></a>

See [Supported Fields per View](/field-rules/jira-administrator/supported-fields-per-view.md) for the fields available on each view. The [Atlassian documentation](https://developer.atlassian.com/platform/forge/apis-reference/jira-api-bridge/uiModifications/#supported-fields-per-view) lists what the platform itself supports and may include newer fields.

## Multiple UIM apps

If you install and configure multiple UIM apps to run for a given combination of space, work type and view type, up to 5 apps can apply changes simultaneously. If more than 5 apps are configured, changes from the remaining apps will be disregarded. Apps apply changes asynchronously, so the order of application is random.

There may be conflicts when multiple apps attempt to modify the same field using the same FieldAPI method. In such cases, users will see corresponding notifications:

*Multiple UI modification apps are trying to change the same field property. If you see unexpected changes to a field, report them to your Jira admin*

If the conflict happens, the changes applied by the app which finished running last will override changes from other apps.

## Need to confirm support?

If you are not sure whether a specific field, view or entry point is covered, [contact our support team](https://forgappify.atlassian.net/servicedesk/customer/portal/2). We will confirm what is supported and, where possible, suggest an alternative setup.