iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
If @forge/react/jira will not resolve, do not change the import path as your first fix. Atlassian documents import { CustomFieldEdit } from '@forge/react/jira'; for Forge custom-field editing with UI Kit components. A project can still fail to resolve that documented path because of its installed dependencies or build setup; the exact cause depends on the error and project configuration.
First identify where the failure happens
Keep the complete error message and note which command or stage produced it. A bundler error saying Module not found or Can't resolve points to a different troubleshooting path than a successfully bundled app that later reports an unknown component or a React hooks/rendering error.
- Build-time resolution error: Inspect the dependency and module-resolution setup for the project that builds the UI Kit entry point.
- Runtime unknown-component error: Check whether the component is being used in the appropriate Forge custom-field module context.
- React hooks or rendering error: Investigate React dependencies and runtime compatibility, but do not assume this explains a build-time package-subpath resolution failure.
Confirm the documented import and intended context
Atlassian’s Jira custom-field documentation and CustomFieldEdit reference show this import:
import { CustomFieldEdit } from '@forge/react/jira';CustomFieldEdit is for building an edit experience for Forge custom fields with UI Kit components. It is not a generic Jira React component path. The fact that Atlassian documents the import confirms the intended usage, but does not confirm that your project has the package installed, has a compatible package version, or uses a resolver that supports it.
#1 Best Overall
If the build cannot resolve the package path
Check dependencies in the app that owns the UI
Open the package.json for the app or workspace package containing the UI Kit entry point, then check its lockfile and installed dependencies for @forge/react. If the dependency is absent, install dependencies from the correct project or workspace root using that project’s package manager, then retry the same build command. If the dependency is present, verify that the build is using that package’s installation and lockfile rather than a different workspace or stale dependency tree.
The documentation does not establish a minimum @forge/react version for this import, so do not treat an arbitrary version upgrade as a guaranteed fix. Record the installed version and use the full error plus the project setup to decide whether a package update or resolver change is actually warranted.
Check the resolver and build configuration
If @forge/react is installed but the exact subpath still fails during bundling, inspect the bundler and its module-resolution configuration, along with the command that triggers the error. The available documentation validates the import for the component; it does not identify a universal bundler configuration or a project-specific patch.
If bundling succeeds but the component is unknown at runtime
Verify that the component is rendered as part of a Forge custom-field edit experience rather than another module or a non-UI-Kit implementation. Atlassian describes CustomFieldEdit for Forge custom-field editing. In one community response to an unknown-component report, a respondent suggested checking the manifest module name and reported using jira:customField. Treat that as an anecdotal diagnostic lead, not a complete official compatibility rule; compare your manifest module with the component’s documented context.
If the error mentions React hooks or rendering
A developer reported resolving a React hooks/rendering error in a Forge-created project by adding react: ^18.2.0 to package.json. That is one reported case, not a universal requirement or verified fix for @forge/react/jira resolution. Consider React dependency alignment only when the symptom is a runtime hooks or rendering failure; it does not by itself explain a bundler’s inability to find the import.
Know what the component does after it loads
In the Jira custom-field documentation’s described experience, CustomFieldEdit calls onSubmit on blur events. The example submits the new field value through view.submit(...). The dedicated reference also lists hideActionButtons, disableSubmitOnBlur, and disableSubmitOnEnter props. Check Atlassian’s current documentation for the exact behavior and context you are implementing, especially because the component is identified there as a preview feature.
Collect these details before applying a project-specific fix
- The complete error text and the command or stage that produced it: build, tunnel, deploy, or app rendering.
- The installed
@forge/reactand React versions, plus the relevantpackage.jsonand lockfile details. - Your package-manager and workspace structure, bundler, and relevant module-resolution configuration.
- The relevant manifest module and whether the component appears in a Forge custom-field UI Kit edit experience.
Without those details, the documented import is a useful baseline, not a diagnosis of a particular project’s failure.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
