Summary
Ensure Jira UI Modifications run for “Create work item” (empty board) and required‑field fallback modals, so Forge Custom Fields can access fields consistently across all work‑item creation flows.

Background / Context
A Forge partner is using Jira UI Modifications together with a Forge Custom Field to implement cross‑field logic on the issue create screen. Their app relies on:
 
 

import { uiModificationsApi } from "@forge/jira-bridge";
uiModificationsApi.onInit(  ({ api }) => {    // init things  },  () => []);
uiModificationsApi.onChange(  ({ change }) => {    // handle change  },  () => []);

This works correctly when issues are created via Global Issue Create (GIC) — e.g. the global “+ Create” button or the c keyboard shortcut.

Per public docs, UIM for GIC currently supports:

• Global Create button
• c keyboard shortcut
• CreateIssueModal from @forge/jira-bridge

Ref: Jira UI modifications

However, the same project/issue type configuration does not trigger UI Modifications for some other creation flows in Jira Software.

Current behaviour

In the following flows, a creation modal is shown but UI Modifications are not executed (partner confirms onInit is never called):

1. “Create work item” on an empty board

• When a board has no issues, the user sees a “Create work item” call‑to‑action.
• Clicking it opens a creation modal.
• The partner’s UIM app does not run; custom logic has no access to fields.

1. Required‑field modal triggered from fast inline creation on a board

• On a board that already has issues, clicking “+ Create” in a column creates an inline issue.
• If a required field is missing, Jira opens a follow‑up modal to collect required fields.
• In this modal, UI Modifications are not triggered either; onInit and onChange never run.

In both cases:

• The user sees what appears to be a “full” (or fuller) create experience.
• The UIM configuration is present for the same project/issue type and works via GIC.
• But the modals shown in these flows do not mount the UIM extension, so Forge apps cannot see or modify fields there.

Expected behaviour (from partner / platform perspective)

For a given project + issue type where UIM is configured:

• All Jira work‑item creation experiences that show a full or near‑full set of fields should either:

• Reuse the Global Issue Create (GIC) implementation with UIM enabled, or
• Mount the UIM extension in an equivalent way,
• So that the UIM app:
• Receives onInit and onChange callbacks,
• Has access to the same field set as in GIC,
• Can apply consistent logic (validation, defaults, dynamic visibility, etc.) regardless of entry point.

Concretely, the partner expects:

• “Create work item” modal on an empty board to trigger the same UIM configuration as GIC.

• The required‑field modal after inline create on boards to also trigger UIM for the relevant project/issue type.