- Update to the Forge edition
- Configurations are transferred automatically
- Checking the result
- If settings did not move automatically
- Move configurations between Forge sites
- Next Steps
The Forge edition of Customer Portal Fields Panel replaces the Connect app on the same Marketplace listing. You do not buy anything again: your subscription and license stay as they are.
Update to the Forge edition
- A Jira administrator opens Apps → Manage apps and finds Customer Portal Fields Panel.
- Click Update.
- Accept the permissions the Forge edition asks for - see the Permissions Reference.
Atlassian stops running Connect apps on 31 January 2027. Update before that date, otherwise the panels disappear from your customer portal. See the Connect to Forge Migration Plan for the plan across all JiBrok apps.
Configurations are transferred automatically
While the Connect app is installed, it saves its settings for the Forge edition on your Atlassian site on a schedule. After the update the Forge edition reads the settings the Connect edition saved and creates its configurations by itself, within about an hour: nobody has to open the settings page. If a Jira administrator opens Customer Portal Fields Panel settings (Jira administration, Apps menu) sooner, the transfer runs right then. Nothing leaves Atlassian.
- One configuration per panel and place. Each field panel becomes a configuration for its portal, with every request type the panel was bound to, the panel’s name, description, “show name”, “show description” and fields in the same order.
- Place. A panel of the main block becomes JSM Portal Panel; a panel of the details sidebar becomes JSM Portal Request Details Sidebar. A panel shown in both places becomes two configurations, “<panel>” and “<panel> - details”.
- Layout and date formats. Hiding empty fields, the colon after the field name, the value under the name and the date and date-time formats are carried over as they were set. An option the Connect panel left unset keeps the Forge default: empty fields shown, colon, value next to the name, dates in the viewer’s locale. See Portal Panel Settings.
- Nothing is overwritten. If a configuration with the same name already exists, it is kept and the Connect one is skipped.
- Same names. Connect configurations that share one name are all transferred: the second becomes “<name> (2)”, the third “<name> (3)”, and so on. Importing the same settings again creates no duplicates.
- Fields. The Forge edition shows at most 50 fields in a panel: the fields after the 50th are not transferred and are named in Settings from Connect.
- Created disabled: a panel no request type was bound to (“was not shown in Connect”), and a panel whose request types belong to no portal.
Actor: check it after the transfer
Connect read request fields as the app. Configurations transferred by themselves, before anyone opened the settings page, get the actor Application (for JSM Portal), as in Connect. If a Jira administrator opened the settings page first, the transferred configurations get that administrator as their actor. With a named actor, customers who are not Jira users do not see the panel. For panels meant for customers, set the actor to Application (for JSM Portal) - see Actor configuration.
What is not transferred
Named for each configuration in Settings from Connect:
- remote issue links and web links;
- linked issues of the panel (link types, linked issue fields, restricting linked projects). Linked requests are available in the Forge edition: set them up again on the configuration’s Linked issues tab - see Data Sources.
Checking the result
The Settings from Connect block on the Bulk Operations tab of Customer Portal Fields Panel settings shows:
- whether settings of the Connect edition were found;
- when they were imported;
- how many configurations were created, skipped or created disabled, and what to check. Configurations that were not created are listed first, each with the reason.
Import again re-runs the transfer and still skips configurations whose name already exists.
While a transfer is already running, the block says “another import of the Connect settings is running - try again in a minute”. A transfer that found the Connect settings in the middle of being saved, or ran out of time, is repeated by itself the next hour.
Then open a request on the customer portal as a customer and check that each panel shows only the intended fields.
If settings did not move automatically
If Settings from Connect says no settings were found - the Connect edition did not save them, it was already removed, or support asked you to - transfer them with a file:
- In the Connect edition, open the project settings, tab Migration to Forge, and select Download for Forge - the file holds the panels of the whole site. Or use the file you received from us. Only a Jira administrator can download it.
- Open the file in a text editor and copy its whole content.
- In Customer Portal Fields Panel settings → Bulk Operations → Settings from Connect, paste the content into the transfer file box and select Import from Connect file. Only a Jira administrator can do this.
The result is the same as the automatic transfer: the same configurations, nothing overwritten (a configuration whose name exists is skipped), the same summary. A large file is imported in batches until it is done - keep the page open. Importing the same file again creates no duplicates.
A file of another app (“This file is for another app”), a changed file or a file that is not valid JSON is refused with the reason, and nothing is imported.
Move configurations between Forge sites
After the transfer, configurations can be exported to JSON or CSV on the Bulk Operations tab and imported on another Forge site. See Bulk Operations.
Next Steps
- Configuration Basics - The configuration form
- Bulk Operations - Export, import and Settings from Connect
- Portal Panel Settings - Link buttons, panel layout, request details sidebar
- JSM Integration - Portal locations and the actor
- Permissions Reference - Scopes the Forge edition asks for

