FAQ

Short answers to common questions. If something does not work as described, see Troubleshooting or contact us.

About

What is PortalPilot?

A Forge app for Jira Service Management Cloud. It adds a full-screen request list to the customer portal, opened from a banner on the portal’s Requests page.

Customers can filter, sort, search, save filters and export. Jira admins configure it from five admin pages.

Where do customers find it?

On the portal’s Requests page, the one that lists all of a customer’s requests across service projects. A banner there has a button that opens PortalPilot full screen.

Admins can change the banner text and button label, or hide the banner.

Does it replace the portal’s Requests page?

No. Jira’s own Requests page stays as it is. PortalPilot opens on top of it and closes back to it.

Does it work on Jira Server or Data Center?

No. PortalPilot is a Forge app and runs on Jira Cloud only.

How do I install it?

A Jira admin installs it from its Atlassian Marketplace listing, with a free trial or a paid subscription. There is no separate installation link. See Install PortalPilot.

Is PortalPilot free?

No. PortalPilot is a paid app, sold through the Atlassian Marketplace, with a free trial through the Marketplace. Atlassian handles billing, renewals and cancellation; Limbus Lab does not bill you directly. See Subscription, trial and licensing.

What happens if our subscription ends?

Customers see “PortalPilot isn’t available on this site right now.” in place of the banner and the full-screen view, and the app refuses every call from the portal. Jira admins can still open the admin pages and change settings. Settings, user scopes and saved filters are kept, and return as they were when the subscription is active again.

Uninstalling the app is different: Atlassian then deletes the app’s stored data. See Subscription, trial and licensing.

Data and permissions

Does any of my data leave Atlassian?

No. The app runs on Atlassian Forge and lists no outside address, so it cannot send data anywhere else. There are no Limbus Lab servers.

Whose permissions apply?

The signed-in person’s. Every list is read from Jira as that person, never as the app. A customer sees the same requests in PortalPilot that Jira would show them anyway.

Work item security levels apply too. There is no setting to show requests a customer could not otherwise see.

What does PortalPilot store?

Only its settings and saved filters, in Forge storage. A saved filter holds its name and its criteria, and is kept under the owner’s account ID. Shared and global filters also hold the owner’s display name.

It does not store request content. Lists are read from Jira each time.

Can PortalPilot create, edit or delete requests?

No. It asks Jira only for permission to read requests, work items, organizations and users, plus its own storage and Atlassian’s personal data reporting. It has no permission to change them.

Does it collect usage statistics?

No. The Data collection tab in General settings says so. There is nothing to turn off.

Using it

Why does the count say “1000+”?

Lists show up to 1,000 matching requests. When more requests match, the count shows “1000+”. Narrow the filters to see the rest.

Which filters can customers use?

Status, Reporter, Request type and Organisations, plus Space and any custom fields an admin turns on as filters. Search matches the summary or a request key such as ABC-123.

Why do the counts next to All requests and My requests not change when I filter?

The counts follow the Status filter only. Other filters change the list, not the counts.

Which columns can I sort by?

Summary and Status. Other columns can be shown but not sorted.

Can customers share saved filters?

Yes, if the admin allows it. In Filters management, Save and share, an admin chooses who may save filters, who may share them and who may share them with everybody. Global filters can be managed only by Jira administrators, or by Jira administrators and selected users or scopes.

How many requests can I export?

Up to the limit the admin sets, which is at most 1,000 requests per export. The admin can also turn export off.

Can I raise a request from PortalPilot?

Yes. Raise a request lists the portals and request types you may raise, and opens Jira’s own create form for the type you choose.

Why does PortalPilot open on the screen I had before?

PortalPilot remembers the last screen in your browser tab for up to 12 hours, so a reload continues where you were. Search text and custom-field filter values are not kept.

Admins

Where is the admin page?

In Jira settings, under Apps, open PortalPilot. Its pages are Get started, General settings, Scopes configuration, Fields configuration and Filters management.

Is the Help Center link on by default?

No. The Help Center link stays hidden until a Jira admin turns it on in the app’s admin pages.

Who can change the settings?

Jira admins only. The admin pages check this on the server for every request. If Jira does not confirm the person is an admin, the change is refused.

Can I limit who sees PortalPilot?

Yes. In General settings, Visibility, choose Everyone or Only selected users. You can allow or deny users, organizations, groups and user scopes. If Jira cannot confirm whether a person belongs to an organization or group, access is denied.

Do Jira admins always see PortalPilot on the portal?

No. Visibility applies to everyone, Jira admins included. There is no admin bypass.

When do my changes reach customers?

Settings apply to the whole site. Customers see a change the next time they load the portal page or open PortalPilot. Visibility, export, field visibility and the Save and share rules are also checked on the server for every action.

Does it support Assets or migration from Server?

No. PortalPilot does not read Assets and has no migration from Server or Data Center.


Need help with PortalPilot? Contact us