What PortalPilot does, how it is set up and the words it uses.
PortalPilot is a Forge app for Jira Service Management Cloud. It gives customers one full-screen list of every request they may see on the portal, with search, filters, saved filters and export. It has two sides.
- Customer side: a banner on the portal’s Requests page opens PortalPilot full screen. Inside, customers see the Pivot overview and their My requests and All requests lists. They can search, filter, sort, save filters, export and raise a request.
- Admin side: the PortalPilot admin page in Jira settings, under Apps. Only Jira admins can open it. Its pages are Get started, General settings, Scopes configuration, Fields configuration and Filters management.
How it fits together
- A Jira admin installs PortalPilot on the site from the Atlassian Marketplace, with a free trial or a paid subscription.
- The admin works through Get started: who can use it, the banner, export, fields and filter sharing.
- Customers open PortalPilot from the banner on the portal’s Requests page.
- Every list is read from Jira as the signed-in customer, so nobody sees more than Jira already lets them see. How PortalPilot works explains this.
Key terms
- View: Pivot, My requests or All requests. The number beside a view is its count.
- Pivot: the overview page with tiles and charts of your requests.
- Visibility: the admin setting that decides who may open PortalPilot.
- Saved filter: a named set of filters, columns, sort and page size.
- Global filter: a saved filter that Jira admins, or people they name, manage for everyone.
- User scope: a named group of users, organisations and groups that admins reuse across settings.
What it does not do
- It does not create, edit or delete requests. Raise a request opens Jira’s own form.
- It does not change who can see a request. Jira decides that.
- It does not read Assets.
- It does not migrate data from Jira Server or Data Center.
Related pages
Need help with PortalPilot? Contact us