# jira:customFieldType + Custom UI + isInline:true — edit resource iframe never loads eagerly on issue-view, only after user click

**URL:** <https://community.developer.atlassian.com/t/jira-customfieldtype-custom-ui-isinline-true-edit-resource-iframe-never-loads-eagerly-on-issue-view-only-after-user-click/102661>\
**Category:** Forge UI Kit and Custom UI\
**Tags:** jira-cloud, rest-api, forge\
**Created:** [September 14, 2026, 6:26am UTC](https://community.developer.atlassian.com/t/jira-customfieldtype-custom-ui-isinline-true-edit-resource-iframe-never-loads-eagerly-on-issue-view-only-after-user-click/102661 "2026-09-14T06:26:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![VikasThakur](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/vikasthakur/32/56184_2.png) [@VikasThakur](https://community.developer.atlassian.com/u/VikasThakur)\
**Post date:** [September 14, 2026, 6:26am UTC](https://community.developer.atlassian.com/t/jira-customfieldtype-custom-ui-isinline-true-edit-resource-iframe-never-loads-eagerly-on-issue-view-only-after-user-click/102661/1 "2026-09-14T06:26:08Z")

</div>

## Summary

For a `jira:customFieldType` field using Custom UI with `isInline: true` and  
`edit.experience` including `issue-view`, the edit resource’s iframe never mounts  
on initial issue-view page load. It only mounts after the user clicks/interacts  
with the field. Before that click, the field area renders completely blank  
(no content, no Jira native fallback, nothing) — confirmed via DevTools Network  
tab by tracking the unique content-hash of the compiled bundle.

This defeats the purpose of isInline (which per the docs should render the  
field inline on issue-view without requiring a modal or a click), for any  
use case where the field’s display depends on data that must be computed  
before the user interacts with it (e.g. a background color driven by a rule  
engine evaluating another field’s value).

## Environment

- Forge CLI: [paste your `forge --version` output]
- Runtime: nodejs22.x (per manifest below — originally nodejs24.x, please confirm  
whichever you’re actually running)
- App type: Custom UI (React 18, Create React App build), not UI Kit
- Jira Cloud ([arzenicstech.atlassian.net](http://arzenicstech.atlassian.net))

## Manifest (relevant excerpt)

```auto
modules:
  jira:customFieldType:
    - key: conditional-color-type
      name: Conditional Color
      description: >
        Text field whose displayed color changes based on another field's
        value (Priority or Status). Configure the rule when adding this
        field to a project.
      type: string
      resolver:
        function: colorFieldResolver
      edit:
        resource: conditional-color-ui
        isInline: true
        experience:
          - issue-create
          - issue-transition
          - issue-view
      contextConfig:
        resource: cc-config-ui

  function:
    - key: colorFieldResolver
      handler: index.conditionalColorResolverHandler

resources:
  - key: conditional-color-ui
    path: static/conditional-color/build

permissions:
  scopes:
    - read:jira-work
    - storage:app
    - manage:jira-configuration
    - manage:jira-project

```

## What we tried, and what we ruled out

1. Originally had a separate `view:` block pointing to a different Custom UI  
resource (`cc-view-ui`), following the pattern shown in the manifest  
reference docs (edit + view both declaring “issue-view”):

2. Before adding the view resource, with no view block at all, the field on  
issue-view (pre-click) rendered Jira’s own generic native fallback  
(confirmed via `data-component-selector="jira-issue-view-single-line-text -inline-edit-view-container"` in the DOM inspector) instead of any Forge  
resource.

3. Removed the `view:` block entirely (current manifest above, edit-only).  
Result: the pre-click blank state changed — Jira’s native fallback no  
longer renders either. Now nothing renders in the field area until click.  
On click, the edit resource’s iframe mounts (confirmed via Network tab,  
`hosted-resources-iframe` testid, matching the expected content-hash) and  
the field then displays correctly with its color logic.

## Question

Is eager/inline rendering of a `jira:customFieldType` Custom UI edit resource  
on issue-view (before any user interaction) actually supported today, or does  
`isInline: true` for Custom UI only affect what happens _after_ the user  
initiates edit (i.e. inline-vs-modal), while the initial _display_ state is  
still gated behind interaction?

If eager rendering is supported, what are we missing in the manifest or  
resource code to trigger it? If it’s not currently supported for Custom UI  
(possibly UI Kit only — noted in an older community thread here:  
[Customfield Custom UI for render/view](https://community.developer.atlassian.com/t/customfield-custom-ui-for-render-view/52762)),  
is there a supported pattern for showing a computed/dynamic background before  
the user clicks the field (e.g. a separate module type that always renders,  
like jira:issuePanel or jira:issueViewBackgroundScript combined with a custom  
field)?

Any pointers appreciated — happy to share a minimal repro repo if useful.

---

<div class="post-metadata">

**Author:** ![Mihai\_leanzero](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/mihai_leanzero/32/55980_2.png) [@Mihai\_leanzero](https://community.developer.atlassian.com/u/Mihai_leanzero)\
**Post date:** [September 14, 2026, 7:43am UTC](https://community.developer.atlassian.com/t/jira-customfieldtype-custom-ui-isinline-true-edit-resource-iframe-never-loads-eagerly-on-issue-view-only-after-user-click/102661/2 "2026-09-14T07:43:36Z")

</div>

Not supported, and that is documented. The custom field type reference carries a note under View mode: custom rendering currently cannot be implemented using Custom UI. The 2021 thread you linked is still the answer, KamilRichert there is Atlassian staff and edit only is what he said. The schema still accepts a Custom UI `view:` block (no `render: native` required), so lint stays quiet and the bundle is not requested at all. Matches your Network tab.

`isInline` does not touch that. CHANGE-2023 words it as inline rendering in edit mode. Inline vs modal, after the click.

Pre-click colour means a UI Kit view. The resource has to be a `@forge/react` entry, teh CRA build will not do:

```yaml
view:
  resource: cc-view-kit
  render: native
  experience:
    - issue-view
resources:
  - key: cc-view-kit
    path: src/frontend/view.jsx

```

Value comes from `useProductContext()`. Keep the Custom UI edit as is, Kamil’s post 4 in that thread describes exactly that split. Untested on my side, so post what happens.

---

<div class="post-metadata">

**Author:** ![VikasThakur](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/vikasthakur/32/56184_2.png) [@VikasThakur](https://community.developer.atlassian.com/u/VikasThakur)\
**Post date:** [September 14, 2026, 1:22pm UTC](https://community.developer.atlassian.com/t/jira-customfieldtype-custom-ui-isinline-true-edit-resource-iframe-never-loads-eagerly-on-issue-view-only-after-user-click/102661/3 "2026-09-14T13:22:16Z")

</div>

Thanks for the help Mihai !