Portal Fields for Jira Service Management
Show customers what is happening with their request: the fields your agents fill in, the SLA timers, the approvals and the status history, right on the help centre request page.
Getting started
- Install Portal Fields from the Atlassian Marketplace on a site with Jira Service Management.
- Open a service project's settings, then Apps, then Portal Fields.
- Pick a request type, or "Default for all request types", and add the fields customers should see. Give each a plain-words label, for example "Handled by" instead of "Assignee". Choose which SLA timers to show and whether approvals and the status history appear.
- Save, then use "Preview as a customer" with a request key to see the result. Customers see the new panel under their request's details the next time they open it.
What customers see
A compact list of the fields you chose, in your order, with your labels. Dates and times are shown in the customer's own time zone. Below the fields, SLA timers appear as cards: "2h 10m left", "Met", "Paused", or "Overdue by 1d". Approvals, when switched on, show the step name, who decides and their decision; the portal already shows approvals on most request types, so this is off by default. The status history lists every status the request has been in, with the time it changed, using the status names customers see on the portal, and is also available from the request's actions menu as "Status history".
Who sees what
Nothing is shown unless a project admin set it up for that request type or for the project default. The app checks that the viewer may see the request before it reads anything: customers see only their own requests and the ones shared with them, as on the portal itself. Fields are read by the app, so agents' fields that customers cannot normally see become visible exactly as you configured, which is the point; choose with care. The settings page marks free-text and people fields with "shown verbatim", and time tracking, parent and environment fields cannot be chosen at all. Comments, attachments, links, restrictions and security levels can never be shown through the app.
| Setting | Who |
|---|---|
| Change what a request type shows | Jira admins, project admins of that service project |
| Preview as a customer | Same |
| See the panel | Anyone who may see the request on the portal: the reporter, request participants, members of an organisation the request is shared with, agents |
Request types and the default
A request type with its own setup uses it. Every other request type uses "Default for all request types" if one exists. Remove a request type's setup to fall back to the default, or remove the default to show nothing for the rest.
Field types
Text, numbers, dates, people, groups, select lists and cascading selects, labels, priorities, rich text (shown as plain text), time tracking, approvals and SLA fields are all rendered. Values the customer cannot be shown, such as assets objects, appear by name when Jira provides one and are otherwise left out. Up to 25 fields per request type; long values are shortened.
Limits
- 25 fields per request type, labels up to 60 characters.
- The status history uses the portal's own status history; very long histories are cut at 500 entries.
- If Jira is slow to answer, the panel says so and asks the customer to refresh rather than showing nothing.
- No data leaves Atlassian: the app runs on Forge with storage in your site's region, and only the per-project setup is stored. See Privacy.
Frequently asked
Can customers edit the fields?
No. The panel is read-only; customers change what the request form allows.
Why does a customer see "Not set"?
The field is in your list but empty on that request. Remove it from the list if that is noise.
Does it work for anonymous portals?
Only for signed-in customers. Anonymous visitors cannot be matched to a request, so the panel stays empty for them.
Changelog
- 1.0 (November 2026): first release.
