Limitations

Field Rules – UI Modifications for Jira is built on Atlassian’s Forge platform, leveraging the UI Modifications API. Because of this, the app’s capabilities are closely tied to the features and limitations of the underlying platform.

Below, you’ll find:

  • A list of project types and view types that are currently supported.

  • A set of feature requests and improvements that depend on Atlassian’s implementation before we can extend support further.

UIM supported project types

UIM support depends on project type and view types. Read full details in the Atlassian documentation.

Global Issue Create

UIM for Global issue create (GIC) currently supports the following project types:

Read more about Global Issue Create's known limitations in the Atlassian documentation.

Supported entry points

The Global issue create (GIC) modal can be opened from many places in the system, currently supported are the following entry points:

  • the global Create button in the top Navigation bar

  • the c keyboard shortcut

  • the issue view Add a child issue and Create subtask buttons

  • a Forge app with custom UI using CreateIssueModal from @forge/jira-bridge

The Global issue create (GIC) modal with UIM will only open from Add a child issue and Create subtask if the summary and at least one other field is set as mandatory for the issue type.

Issue View

UIM for Issue view currently support the following project types:

Supported entry points

The Issue view can be displayed in many places in Jira, currently supported are:

  • Full page issue view

  • Board issue view

  • Backlog issue view

  • List issue view

  • Issues issue view

  • Search issue view (global search)

Read more about Issue View's known limitations in Atlassian documentation.

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 currently support the following project types:

Supported entry points

The Issue transition dialog can be opened from many places in the system, currently supported are the following entry points:

  • full page Issue view:

    • changing the issue status

    • running edit status from the command palette

  • all issues page - changing issue status

  • Project > Backlog - changing the issue status

  • Plans > Timeline - changing the issue status

  • Active sprints - moving card between columns

  • Active sprints - issue dialog changing the issue status

Supported fields per view

The app aims to handle all currently UIM supported fields. The full list can be found in the Atlassian documentation.

Multiple UIM apps

If you install and configure multiple UIM apps to run for a given combination of project, issue 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.

Known platform errors

Story Points field

UI Modifications do not work for the Story Points field on the Issue View.

Even if the field is correctly added to the screen, any UI Modifications applied to it will not take effect on the Issue View.

This is a known platform limitation.

To help us push for a resolution, please vote on the Atlassian ticket here: FRGE-1736 – Story Points field not affected by UI Modifications

Open Feature Requests (Pending Atlassian Platform Support)

Below is a table of open Atlassian feature requests that impact the capabilities of our Field Rules – UI Modifications for Jira app. Once Atlassian implements these features, we'll be able to enhance the app accordingly. If you care about any of these items, please vote and comment to help prioritize them.

Ticket ID
Summary
Status

JSM portal support

In Progress

Support for Assets field

Reviewing

Support for Project field

Reviewing

Support for Team field

Reviewing

Support for Project picker field

Reviewing

Support for Due date field on Issue View and Issue Transition

Reviewing

Story Points field not affected by UI Modifications

Needs Triage

Support for Cascading Select field

Reviewing

Support setOptionsVisibility for Affects versions and Fix versions fields

Reviewing

Additional support to Issue Type field

Reviewing

onChange callback is not triggered consistently when last checkbox is selected

Needs Triage

UIM on IssueView does not update multi select fields consistently

Gathering Impact

Support for fields created with Forge

Future Consideration

How You Can Help

Atlassian pays attention to community interest when prioritizing new features. If any of the above items would benefit your team:

  • Vote on the issue in the Atlassian tracker to signal demand.

  • Comment with your specific use case—real-world scenarios make a big difference.

  • Watch or follow the issue to stay updated on progress.

Your engagement can help speed up the delivery of these features—and once they’re available, we’ll roll out enhancements to our app right away.

Last updated