Fields Panel for JSM - Forge edition

Cloud This page documents the Connect build of Fields panel for Jira Service Management. Looking for the current Cloud app? See Customer Portal Fields Panel (Forge) for JSM.

Update to the Forge edition

The Forge edition of Fields Panel for JSM ships on the same Marketplace listing as the Connect edition. To move to it, open Manage apps in Jira and click Update on Fields Panel for JSM. You do not buy anything again and you keep your license.

Atlassian ends support for Connect apps on 31 January 2027. See the Connect to Forge Migration Plan for the plan across all JiBrok apps.

The project settings of the Connect edition show a Forge edition is available banner.


Where panels appear on the portal

The Forge edition shows your panels in these places of the Jira Service Management customer portal:

Location Portal pages
Request details panel - in the body of the request page View request
Request details sidebar - in the side column of the request page, next to the request details View request
Portal header View request
Portal subheader View request, Create request
Portal footer View request, Create request

Portal customers see the panels, and so do unlicensed users of the portal.

Request details sidebar

The sidebar puts a fields panel in the side column of the request page, next to the request’s own details. It is the Forge counterpart of the Connect panel in the request details (the topPanelId location).

SLA on the portal

The request details sidebar also shows the request’s SLA, so a customer sees the service level of their request on the portal next to the fields you chose.


Your Connect panels

While the Connect app is installed, it saves its settings for the Forge edition on your site on a schedule. After the update the Forge edition reads them 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 sooner, the transfer runs right then. Nothing leaves Atlassian.

The result appears in the Settings from Connect block on the Bulk Operations tab, with Import again. If no settings were found, a Jira administrator downloads the transfer file in the Connect edition - project settings, tab Migration to Forge, Download for Forge; the file holds the panels of the whole site - and pastes it into Settings from Connect with Import from Connect file.

How panels become configurations

  • Each pair “panel × location” becomes one configuration, with every request type the panel was bound to.
  • A panel shown in both locations becomes two configurations: <name> and <name> - details.
  • The Connect top panel (topPanelId) has its own location in the Forge edition - the request details sidebar.
  • A panel with no bindings is created disabled (“was not shown in Connect”), and so is a panel whose request types belong to no portal.
  • Panels with the same name are all transferred: the second becomes “<name> (2)”, the third “<name> (3)”.
  • The actor: configurations transferred by themselves get Application (for JSM Portal), as in Connect, where the app read request fields; if a Jira administrator opened the settings first, that administrator. With a named actor, customers who are not Jira users do not see the panel.

What is migrated

  • Name and description
  • Show name and show description
  • Fields, in their previous order (up to 50)
  • Request types and portal
  • Hiding empty fields, the colon after the field name, the value under the name
  • Date and date-time formats

What is not migrated

  • Remote issue links and web links
  • Linked issues of the panel - link types, linked issue fields, restricting linked projects; set them up again on the Linked issues tab

Details - Moving from the Connect edition.


Linked issues on the portal

When a configuration shows linked issues on the portal, a portal customer sees a linked issue only if:

  • it is a Jira Service Management request, and
  • the customer is its reporter or a participant, or the request is shared with the customer’s organization.

If any of these checks fails with an error, the issue is not shown. Ordinary (non-JSM) linked issues are never shown on the portal. The link opens the request on the portal, not the /browse/ page.


Next steps