- Overview
- Enabling JSM Modules
- Portal Request Detail Panel
- Portal Request Details Sidebar
- Portal Header
- Portal Footer
- Portal Subheader
- Filtering by Request Type
- Portal Filtering
- Unlicensed Access
- Best Practices
- Troubleshooting
- Next Steps
Show fields of the request, linked requests and link buttons on the customer-facing Jira Service Management portal.
Overview
Customer Portal Fields Panel supports five JSM portal locations:
| Module | Location |
|---|---|
| JSM Portal Panel | Request page, main column |
| JSM Portal Request Details Sidebar | Request page, right-hand details column, next to the request details |
| JSM Portal Header | Request page, above the page title |
| JSM Portal Subheader | Request page, below the page title |
| JSM Portal Footer | Request page, bottom |
Request pages only. Panels are not shown on the portal home page, the request list or the request create form.
Panel layout, link buttons and how request fields are shown are described in Portal Panel Settings.
Enabling JSM Modules
- Go to Apps → Customer Portal Fields Panel settings
- Click Module Settings tab
- Enable JSM modules:
- JSM Portal Panel
- JSM Portal Request Details Sidebar
- JSM Portal Header
- JSM Portal Subheader
- JSM Portal Footer
- Click Save
Portal Request Detail Panel
Displays on the request details page when customers view their requests.
Configuration
- Create new configuration
- Select JSM Portal Panel as Display Module
- Choose the display fields and, if needed, linked requests
- Set context filters (portals, request types)
- Save
Portal Request Details Sidebar
Displays 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.
Configuration
- Create new configuration
- Select JSM Portal Request Details Sidebar as Display Module
- Choose the display fields
- Set context filters (portals, request types)
- Save
Panels that the Connect edition showed in the details sidebar are transferred to this location - see Moving from the Connect edition.
Portal Header
Displays above the page title of the request page.
Configuration
- Create new configuration
- Select JSM Portal Header as Display Module
- Choose the display fields or link buttons
- Save
Portal Footer
Displays at the bottom of the request details page.
Configuration
- Create new configuration
- Select JSM Portal Footer as Display Module
- Choose the display fields or link buttons
- Save
Portal Subheader
Displays below the page title of the request page.
Configuration
- Create new configuration
- Select JSM Portal Subheader as Display Module
- Choose the display fields or link buttons
- Save
Filtering by Request Type
Show panels only for specific request types.
Configuration
- Edit your JSM panel configuration
- Go to Context tab
- Find Show only for request types
- Select request types from your service desks
Example
Filter for “IT Help” and “Hardware Request” → Panel only appears for those request types.
Portal Filtering
Restrict configurations to specific JSM customer portals.
How Portal Filtering Works
Portal filtering is the JSM equivalent of project filtering. It restricts which customer portals show the panel.
- Empty portals list: Shows on all portals
- Selected portals: Shows only on selected portals
Configuration
- Edit your JSM configuration
- Go to Context tab
- Find Show only in portals
- Select one or more portals
The request type list is narrowed to the selected portals.
Unlicensed Access
JSM portal modules support unlicensed access, meaning customers viewing the portal don’t need a Jira license to see panel content. This is handled automatically by the app.
Actor Configuration for Portal Panels
The Actor of a configuration (tab Other) is the account the panel reads Jira data as.
| Actor | Who sees the panel’s data |
|---|---|
| Application (for JSM Portal) | All portal viewers, including customers who are not Jira users. The panel reads as the app; comments and attachments are filtered as described in Fields on the Portal, linked requests are shown only when the customer may see them |
| A named account | Portal viewers who are Jira users (for example agents). The panel reads with that account’s permissions. Customers who are not Jira users do not see this panel |
| Empty (default) | The panel reads as the viewer. Customers who are not Jira users see such a panel only when it shows static content: no fields, no linked requests |
Application (for JSM Portal) is offered for the Portal Panel, Request Details Sidebar, Subheader and Footer, not for the Header.
Use a dedicated account. For a named actor, use a service account with minimal permissions, never a powerful admin account. The actor is set only by a Jira administrator on Customer Portal Fields Panel settings; it is not available on the project settings page and is not exported with configurations.
Tip: With Application (for JSM Portal) every portal visitor sees the same fields. Any field you select, other than comments and attachments, is shown to customers as it is - see Admin Hardening - JSM portal specifics.
Best Practices
- Select only the fields customers need - every selected field reaches the customer’s browser
- Mind the warnings the form shows for comments, attachments, work log, issue links and subtasks
- Use the request details sidebar for a short list of key fields
- Test how panels appear in the customer portal, logged in as a customer
Troubleshooting
Panel Not Showing on Portal
- Check that the location is enabled in Module Settings
- Check the Actor - customers who are not Jira users see the panel only with Application (for JSM Portal)
- Verify the panel targets the correct portals and request types
- Log in as a customer to test visibility
If a panel cannot be loaded, its location stays empty instead of showing an error to customers.
Panel Shows for Wrong Requests
- Review the request type filter
- Check the portals filter
- Verify the Display JQL condition
Next Steps
- Portal Panel Settings - Link buttons, panel layout, request details sidebar, fields on the portal
- Context Filters - Filter by portals and request types
- FAQ - JSM portal troubleshooting
- Permissions Reference - Portal access and permissions

