What to check when the banner, a field, export or saving is missing, or a rule does not match.
Customers see “PortalPilot isn’t available on this site right now.”
The site has no active PortalPilot trial or subscription. Customers see this in place of the banner and the full-screen view, and the app refuses every call from the portal.
- A Jira admin sees the warning “PortalPilot subscription is inactive” on the PortalPilot admin pages.
- Renew or manage the subscription in Jira under Apps, Manage your apps. Customers get PortalPilot back, with its settings and saved filters, once it is active again.
See Subscription, trial and licensing.
A customer does not see the banner
- Check that Show the banner is on in General settings, Banner.
- Check Visibility in General settings. People who are not allowed never see the banner.
- Check that the customer is signed in, and is on the portal’s Requests page (the page that lists all their requests).
A customer is told they cannot use PortalPilot
The message is “PortalPilot is not available to your account.” or “You do not have access to PortalPilot.”
- Check both Visibility lists. Can’t access always wins, and a non-empty Can access list admits only its members.
- Jira admins are not let through automatically. Add them like anyone else.
An organisation or group rule does not match
- PortalPilot asks Jira, as the customer, which organisations and groups they belong to. If Jira does not answer, the rule fails closed: a Can access rule refuses, and a Can’t access rule also refuses.
- Check the customer really is in that organisation or group in Jira.
- Test with a real customer account. Users, and scopes made of users, are always checked reliably.
- If the rule uses a scope, check the scope’s members in Scopes configuration.
A field or column is missing
- In Fields configuration, check that Column is on to offer it as a column, or Filtering criteria to offer it as a filter.
- A custom field offered as a column must still be added by the customer in the column picker.
- Check the field’s Visibility. With Only selected scopes, only members of those scopes see it.
- At most 30 custom fields can be configured. To free a slot, set a configured custom field back to its defaults: Column off, Filtering criteria off, its Jira name as the display name, and Visibility set to Everyone. There is no reset or remove button.
A custom field column is empty
- The field shows a value only on requests whose form includes it.
- Check the field’s Visibility in Fields configuration.
Export is missing
- Check that Allow customers to export requests is on in General settings, Export.
- If export was turned off while PortalPilot was open, the export fails with “Export is turned off by your administrator.” Reload the page.
Save filter is missing or cannot share
- Save filter as appears only for people the Saving filters rule allows. Check Filters management, Save and share.
- The Shared with choice appears only for people the Sharing filters rule allows. Everyone on this site also needs the Sharing with everybody rule.
- Save filter as global appears only for Jira admins and the people named in Global filters: who can manage.
- The site holds up to 100 shared and global filters, and each person up to 50 of their own.
Pivot, the counts or the Help Center link are missing
- Pivot: check Show Pivot overview under Navigation on the Visibility tab.
- Counts: check Show total number of requests on the Visibility tab.
- Help Center link: check Show Help Center link under Navigation.
A change does not show yet
- Customers see a change the next time they load the portal page or open PortalPilot.
- A customer who reopens PortalPilot in the same browser tab within 12 hours continues on their last screen, so a new Open PortalPilot on choice may not show for them until then.
A scope cannot be deleted
It is still used by a visibility list, a field or a filter permission. Its badge in Scopes configuration says where. Remove it there first.
A request is missing from the list
- The list is read as the customer. If Jira does not show them the request, PortalPilot does not either.
- Only 1,000 matching requests are listed. Narrow the filters.
Too many filters
“Too many filters or saved filters. Remove some and try again.” means the filter has more than 12 organisation and request type (or space) combinations, or the person already has 50 saved filters.
Messages on the admin pages
A message under a field shows while you edit. The tab shows a Fix label, the save bar says “Fix the highlighted fields to save.” and Save changes stays off until it is fixed. Other messages show in the save bar or a dialog after Jira or the app refuses a change. If a page cannot load, it shows “This page could not be loaded” with the reason and Try again.
Access and connection
- “Only Jira administrators can change these settings.” Your account is not a Jira admin. Ask a Jira admin to make the change.
- “We could not confirm that you are a Jira administrator. Reload the page and try again.” Jira did not answer the admin check, so nothing was saved.
- “The app could not be reached. Check your connection and try again.”
- “Jira did not return the requested data. Try again, or check your permissions.” Jira refused or failed a request the page needs. If it keeps happening, check that your account can see that data in Jira.
- “This item no longer exists. Reload the page.” Someone else deleted it. Reload to see the current list.
- “A selected scope no longer exists. Reload the page and try again.” A scope was deleted while you were editing. Reload and choose again.
- “One of the values is not valid. Check the form and try again.” or “Something went wrong. Try again.” Reload the page and try again.
General settings
- Visibility: “The selected users, organisations or groups are not valid or there are too many.” Each list takes up to 100 users, 50 organisations, 50 groups and 20 scopes. Remove some, or group them in a scope.
- Statuses that mean “waiting on the customer”: “Use 50 statuses or fewer.” or “Each status name must be 100 characters or fewer.” Remove statuses or shorten the name.
- Export: “Enter a whole number from 1 to 1000.” The maximum number of requests per export is empty, not a whole number, or outside 1 to 1000. The server says the same as “The export limit must be a whole number from 1 to 1000.”
- Banner: “Enter the button text.” or “Use 24 characters or fewer.” for the button, and “Use 500 characters or fewer.” for the banner text. The server says “Button text must be 1 to 24 characters.” or “Banner text is too long.”
- Header link, with Custom link: “Enter a name for the link.” or “Use 24 characters or fewer.” for the name. “Enter a full link that starts with https://” for the link: use a full https:// address of up to 500 characters, with no user name or password in it. The server says “The link name must be 1 to 24 characters.” or “Enter a link that starts with https://.”
Scopes configuration
- “Enter a name.” or “Use 40 characters or fewer.” A scope name has 1 to 40 characters. The server says “Enter a name of 1 to 40 characters.”
- “A scope with this name already exists.” Scope names must be unique, ignoring case. Choose another name.
- “You have reached the maximum number of scopes.” The site holds up to 50 scopes. Delete one you no longer use.
- “The selected users, organisations or groups are not valid or there are too many.” A scope takes up to 100 users, 50 organisations and 50 groups.
- “This scope is still used by a setting. Remove it there first.” The scope is in a visibility list, a field or a filter permission. The delete dialog says the same and offers no Delete button.
Fields configuration
- “Enter a name.” The display name is empty. Type a name of up to 40 characters.
- “Select at least one scope, or the field is hidden from everyone.” The field’s Visibility is Only selected scopes with none picked. Pick a scope, or choose Everyone.
- Limit of 30 custom fields reached: a note on the row says so, and the other custom fields cannot be switched on. If a save goes over the limit, the save bar says the fields configuration is not valid, because the limit counts every configured custom field. To free a slot, set a configured custom field back to its defaults: Column off, Filtering criteria off, its Jira name as the display name, and Visibility set to Everyone. There is no reset or remove button.
- “One of the fields is not valid.” A display name is empty or too long. Fix it, or reload the page.
Filters management
- Rename a global filter: “Use 1 to 36 characters.” The server says “Enter a name of 1 to 36 characters.”
- “The filter list changed while loading. Reload the page and try again.” Filters changed while Load more filters was reading. Reload the page.
- Save and share: “The selected users, organisations or groups are not valid or there are too many.” Each list takes up to 100 users and 20 scopes.
Searching for people, organisations or groups
- “The search text is too long.” Search text in these pickers can be up to 60 characters.
Related pages
Need help with PortalPilot? Contact us