Skip to content
Creet / Portal Request View Plus
Overview Help Terms Privacy Security

Help

Setup guide for Jira administrators. Last updated: 13 November 2026.

In short: install the app from the Atlassian Marketplace, then open Jira settings, then Apps, then Portal Request View Plus. Pick a service project and a request type, switch on what customers should see, and save. Nothing is shown anywhere until you switch a request type on.

Set up in five minutes

  1. Install the app. Open the Marketplace listing and select Try it free, or find Portal Request View Plus under Apps, Explore more apps in Jira. You need to be a site administrator. It is free for sites with up to 10 users.
  2. Open the settings page. In Jira, select the cog, then Apps, then Portal Request View Plus in the left sidebar. You need to be a Jira administrator.
  3. Pick a request type. Choose the service project. The page lists every request type with whether it shows the panel, what customers see and who sees it. Select Set up or Edit on one. Settings are kept per request type.
  4. Switch the panel on. On the Panel tab, turn on Show the panel on this request type. Then use the other tabs for the parts you want: Assignee, Service targets, Linked requests and Fields.
  5. Check the preview. What customers will see, beside the tabs, shows a real request with your settings before you save them. See Preview.
  6. Save. Customers see the change within about five minutes. Unsaved changes shows next to the request type's name until you do.
  7. Optional: copy it across. Apply to all request types writes the same settings to every request type in the project. Request types you add later start switched off.

What each part shows

  • Who is working on it: the assignee's display name, or "No one yet". Never an email address or account ID.
  • Service targets: each SLA as On track, Due soon, Overdue, On hold, Met or Missed, with time left, an optional progress bar and due time, and an optional goal. Pick which SLAs customers see from the list (leave it empty to show all), and give each one the name customers see, for example "Time to resolution - P1 internal" as "Resolution target".
  • Linked requests: key, summary, status and the relationship, for example "is blocked by", for linked requests the customer can open themselves. The summary opens that request. Each linked request is checked as the customer, so a request they cannot open is never named. For those you choose: hide them (the default), or switch on Show the status of linked issues the customer can't open to show a row such as "Is blocked by · another request · In progress". By default only issues in the same service project are considered; turning that off lets links to other projects, such as a development board, appear as status-only rows.
  • Extra fields: read-only fields you pick, with your own names, grouped under your own headings, in your order.

Preview

The preview on the settings page shows the panel for a real request of the request type you are editing, using the settings in the form, including ones you have not saved. It picks the newest request of that type; type another request key and select Show to change it.

  • View as shows what an agent, a customer in no organization, or a customer in one of your organizations would see. Use it to check audience rules.
  • It only shows requests you can open yourself. Being a Jira administrator is not enough: if you cannot open a request in the help centre, it cannot be previewed.
  • If the panel is switched off, the preview still shows what customers would see once you switch it on.
  • No request of this type yet? Raise one in the help centre, then come back.

Show it to some customers only

Every part has an Only for these organizations list, and the panel as a whole has Who sees the panel. These use your Jira Service Management customer organizations.

  • Empty means everyone. With no organization selected, everyone who can open the request sees it.
  • Pick organizations to narrow it. A customer sees that part only if they belong to at least one of the selected organizations. Example: show service targets only to your premium-plan organization, or pilot the whole panel with one friendly customer first.
  • Agents always see everything, so you can preview the customer view from the help centre.
  • If membership cannot be checked, restricted parts are hidden. Parts without a restriction still show.

Organizations are managed in your service project under Customers. After an upgrade that added this feature, a site administrator must accept the app's new permission (reading customer organizations) under Apps, Manage apps before the lists load.

Which fields customers can see

Field typeShown as
Text, paragraph and rich textPlain text, up to 500 characters
NumberThe number
Date, date and timeThe date in the customer's own language and time zone, for example "30 Oct 2026, 2:00 PM"
Single select, radio buttons, checkboxes, multi-selectThe chosen option names
Cascading select"Parent / Child"
User picker (single or multiple)Display names only
Version, component, priority, status, labels, groupTheir names
Assets objects and other app-specific fieldsNothing. The picker marks these "May show blank".
SLA fieldsUse the Service targets switch instead

Never shown, whatever the settings: comments, worklogs, time tracking, attachments, reporter, creator, watchers, votes, security level, sub-tasks and parent. These are blocked in the app's code, not just hidden in the settings page.

Troubleshooting

  • The panel does not appear at all. Check that the request type is switched on, that Who sees the panel includes the customer's organization or is empty, and that the customer can open the request. Logged-out visitors never see the panel.
  • A "Request details" heading appears with nothing under it. Jira draws the heading for every request type once the app is installed. Switch the panel on for all request types (use Apply to all request types) so every request shows content.
  • The panel is empty on every request type, even when switched on. The app's own user may not be able to read the project. In the project's permission scheme, Browse Projects must include the project role atlassian-addons-project-access. Default schemes include it.
  • A linked request is missing. The customer cannot open it in the help centre, so it is hidden. Switch on Show the status of linked issues the customer can't open on the Linked requests tab to show its relationship and status without naming it. Agents see more linked requests than customers do, because they can open more.
  • A field shows nothing. It is empty on that request, or it is a type marked "May show blank" in the picker.
  • The organization lists say they could not be loaded. Accept the app's new permission under Apps, Manage apps, then reload the settings page.
  • The settings page says the licence is not active. Customers do not see the panel until the subscription is active again. Your settings are kept.

Support

Email support@creet.in with your site URL and what you expected to see. We reply within 2 working days (Monday to Friday, India Standard Time, UTC+5:30). Please do not send customer request contents unless we ask for them. How the app handles data is described in the privacy policy.

© 2026 Portal Request View Plus, made by Creet

Help Terms Privacy Security Atlassian Marketplace support@creet.in