# 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](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-ui-modifications/#supported-project-types). ### Global Issue Create UIM for Global issue create (GIC) currently supports the following project types: * company-managed and team-managed [Jira Software](https://support.atlassian.com/jira-software-cloud/docs/what-are-team-managed-and-company-managed-projects/) * company-managed and team-managed [Jira Work Management](https://support.atlassian.com/jira-work-management/docs/learn-how-company-managed-and-team-managed-projects-differ/) Read more about Global Issue Create's known limitations in the [Atlassian documentation](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-ui-modifications/#supported-project-types). #### 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.* {% hint style="warning" %} We are awaiting for support of the **Create linked issue** entry point: {% endhint %} ### Issue View UIM for Issue view currently support the following project types: * company-managed and team-managed [Jira Software](https://support.atlassian.com/jira-software-cloud/docs/what-are-team-managed-and-company-managed-projects/) {% hint style="info" %} Vote on support for Jira Work Management: {% endhint %} #### 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](https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-ui-modifications/#issue-view--preview-). ### 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: * company-managed [Jira Software](https://support.atlassian.com/jira-software-cloud/docs/what-are-team-managed-and-company-managed-projects/) #### 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](https://developer.atlassian.com/platform/forge/apis-reference/jira-api-bridge/uiModifications/#supported-fields-per-view). ## 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](https://developer.atlassian.com/platform/forge/apis-reference/jira-api-bridge/uiModifications/#common-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](https://ecosystem.atlassian.net/browse/FRGE-1736) ## 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 | | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | ------------------ | | [ECO-1416](https://jira.atlassian.com/browse/ECO-1416) | Issue View support for Jira Work Management projects | Gathering Interest | | [FRGE-774](https://ecosystem.atlassian.net/browse/FRGE-774) | JSM portal support | In Progress | | [FRGE-978](https://ecosystem.atlassian.net/browse/FRGE-978) | Support for Create issue from board (entry point) | Gathering Interest | | [FRGE-1757](https://ecosystem.atlassian.net/browse/FRGE-1757) | Support for Team field | Reviewing | | [FRGE-1736](https://ecosystem.atlassian.net/browse/FRGE-1736) | Story Points field not affected by UI Modifications | Needs Triage | | [FRGE-1496](https://ecosystem.atlassian.net/browse/FRGE-1496) | Support for Cascading Select field | Reviewing | | [FRGE-1553](https://ecosystem.atlassian.net/browse/FRGE-1553) | Support setOptionsVisibility for Affects versions and Fix versions fields | Reviewing | | [FRGE-1273](https://ecosystem.atlassian.net/browse/FRGE-1273) | Additional support to Issue Type field | Reviewing | | [FRGE-1896](https://ecosystem.atlassian.net/browse/FRGE-1896) | onChange callback is not triggered consistently when last checkbox is selected | Needs Triage | | [FRGE-1420](https://ecosystem.atlassian.net/browse/FRGE-1420) | UIM on IssueView does not update multi select fields consistently | Gathering Impact | | [FRGE-1897](https://ecosystem.atlassian.net/browse/FRGE-1897) | Support for Due date field on Issue View and Issue Transition | Reviewing | | [FRGE-1220](https://ecosystem.atlassian.net/browse/FRGE-1220) | Support for fields created with Forge | In Progress | | [FRGE-1740](https://ecosystem.atlassian.net/browse/FRGE-1740), [FRGE-1773](https://ecosystem.atlassian.net/browse/FRGE-1773) | Support for Project picker field | Done | | [FRGE-2024](https://ecosystem.atlassian.net/browse/FRGE-2024) | Support for Time Tracking fields | Reviewing | | [FRGE-2034](https://ecosystem.atlassian.net/browse/FRGE-2034) | Support for reading Status field on GIC (Create Issue) | Reviewing | | [FRGE-2079](https://ecosystem.atlassian.net/browse/FRGE-2079) | Support for Asset fields | Reviewing | #### 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.