- Request Details Sidebar
- Fields on the Portal
- Panel Layout and Date Formats
- Link Buttons
- Linked Requests
- Translations
- Next Steps
Settings that shape what a customer sees in a panel on the Jira Service Management customer portal. They are part of the configuration form, next to the basic settings and the context filters.
Request Details Sidebar
JSM Portal Request Details Sidebar shows a panel in the right-hand column of the request page, next to the request details - for example, a short list of key fields of the request. It is configured like any other panel: choose it in Display Module.
Panels that the Connect edition showed in the details sidebar are transferred to this location - see Moving from the Connect edition.
All portal locations:
| Display module | Where | Description in the form |
|---|---|---|
| JSM Portal Panel | Request detail page, main column | Request detail page |
| JSM Portal Request Details Sidebar | Right-hand details column of the request page | Request details sidebar |
| JSM Portal Header | Above the page title | Above portal page title |
| JSM Portal Subheader | Below the page title | Below portal page title |
| JSM Portal Footer | Bottom of the page | Bottom of portal pages |
Fields on the Portal
The Additional fields to display of a configuration (tab Display Fields, up to 50) are shown to customers as “name: value”, in the selected order. Values are shown the way Jira users know them: users with avatars, dates in the viewer’s format (or the panel’s date format), options, lists.
Service Management fields
| Field | Shown as |
|---|---|
| SLA | The time of the current cycle (or of the last completed one) with a state icon: met or breached for a completed cycle, running or paused for an ongoing one. A breached ongoing SLA is shown as a red label. The tooltip shows “<time> left” and “Due: <date>”, under the value “within <goal>”. No cycle: “-“ |
| Request language | The language name |
| Responders | Users with avatar and name, teams and groups as labels |
| Approvals | Approval state |
| Request type | Request type icon and name |
| Assets objects | Object names as labels |
| Attachments | List of attachments, see below |
What customers do not see
A panel whose actor is Application (for JSM Portal) reads the request as the app. To keep internal data off the portal:
- Comments - only comments marked public (shared with the customer).
- Attachments - only attachments added by the reporter and attachments of public comments.
- Only the fields selected in the configuration reach the customer’s browser.
The configuration form warns when a selected field (comments, attachments, work log, issue links, subtasks) can show customers more than intended. Choose the display fields of a portal panel with this in mind: any other field you select is shown to customers as it is. See Actor configuration.
Panel Layout and Date Formats
The Layout block (“How the display fields are shown in the panel.”) is on the Display Fields tab and appears once at least one display field is selected.
| Setting | Default for a new panel | What it does |
|---|---|---|
| Show empty fields | on | Off: fields without a value (empty text, empty list) are not shown |
| Colon after the field name | on | “Name: value” or “Name value” |
| Value under the field name | off | On: the value is on its own line under the name |
| Date format | empty | Pattern for date fields, for example dd/MMM/yy |
| Date-time format | empty | Pattern for date-time fields, for example dd/MMM/yy h:mm a |
Date patterns use the Java SimpleDateFormat letters, up to 64 characters. Empty means the format of the viewer’s locale. An invalid pattern falls back to the default format. Date-only fields are shown as the calendar date set in Jira, without a time zone shift.
Panels transferred from the Connect edition keep the layout and date formats they had there.
Link Buttons
Link buttons (“Buttons shown in the section that open a URL in a new tab.”) are set on the Other tab of a configuration. They are shown at the top of the panel.
- Up to 5 buttons per panel (Add link button).
- Label - up to 60 characters, for example “Open in CRM”.
- URL - up to 2,000 characters, must start with
http://orhttps://. - Appearance - Default or Primary.
The URL can contain values of the current request:
| Placeholder | Value |
|---|---|
{issueKey} |
Key of the request |
{issueId} |
ID of the request |
{projectKey} |
Project key |
{portalId} |
Portal ID |
{requestTypeId} |
Request type ID |
Placeholders are allowed after the host name only and are URL-encoded. If a value is missing, the button is not shown.
Linked Requests
A panel can show a table of requests linked to the current request: Linked issues by: Link types on the Linked issues tab, limited to the link types chosen in Link types for filtering. Select at least one link type - with none chosen the table shows no requests.
A linked request is shown to a customer only when the customer may see it on the portal:
- it is a Service Management request, and
- the customer is its reporter or a participant, or belongs to an organization the request is shared with.
If this cannot be checked, the request is not shown. The count shows the number of rows the customer sees. Keys open the request on the customer portal; a request without a portal link is shown as plain text. There is no Issue Navigator link on the portal.
This check applies to panels whose actor reads data on behalf of the customer (Application (for JSM Portal) or a named account). Without an actor the panel reads as the viewer, who sees only what Jira lets them see. Up to 50 linked requests are loaded per panel. See Data Sources.
Translations
The Translations tab holds texts of the panel in other languages, up to 10 languages: name, description, field names, field values (“value -> translation” pairs) and link button labels. Add translation picks a language; below, each text is shown with its source (read-only) and an input for the translation; Delete translation removes the chosen language. Empty inputs keep the source text.
Translations are chosen by the viewer’s language, each text on its own: exact language (for example de-DE), then the base language (de), then the original text. On the portal the language is the one the customer uses on the portal, otherwise the language of their profile.
Next Steps
- JSM Integration - Portal locations and the actor
- Configuration Basics - The configuration form
- Context Filters - Portals, request types and JQL
- Moving from the Connect edition - Settings from Connect

