FAQ & Troubleshooting

Installation & Setup

The app is installed but I don’t see any panels

  1. Go to Apps → Customer Portal Fields Panel settings
  2. Check the Module Settings tab - ensure the desired modules are enabled
  3. Create at least one panel configuration with Configuration Basics
  4. Verify the configuration is Enabled (toggle is on)
  5. Check that the configuration targets the correct portal and request type

What permissions are needed to install the app?

Only Jira site administrators can install apps from the Atlassian Marketplace. After installation, site admins can use Delegation to allow project admins to manage configurations for their projects.

Modules are not appearing in the expected locations

  1. Verify modules are enabled in Module Settings
  2. After enabling a module, refresh the request page on the portal
  3. Check that your browser is not caching old content (try hard refresh)

Panels Not Showing

If a panel isn’t appearing where you expect it, work through this checklist:

Diagnostic Checklist

  1. Is the module enabled?
    • Go to Module Settings and verify the target module is toggled on
  2. Is the configuration enabled?
    • Open the configuration and check the Enabled toggle
  3. Do context filters match?
    • Check Portal filter (JSM) - does the portal match?
    • Check Request Type filter (JSM) - does the request type match?
  4. Does the Display JQL match?
    • Test the Display JQL in Jira’s Issue Navigator with the specific issue

Tip: Use the Test Context button in the configuration editor to check all conditions for a specific issue at once.


JSM Portal Issues

Panel not showing on portal

  1. Verify the location is switched on in Module Settings
  2. Check the Portal and Request Type filters in context settings - empty means all portals and all request types
  3. Check the panel’s Actor: customers who are not Jira users see a panel only when the actor is Application (for JSM Portal)
  4. Clear browser cache and reload the portal page

If a panel cannot be loaded, its location stays empty - customers do not see an error.

Customers can’t see the panel

  • JSM portal panels use unlicensed access - customers don’t need a Jira license
  • Set the actor to Application (for JSM Portal) for panels meant for customers. With a named actor, customers who are not Jira users do not see the panel; with no actor they see it only when it shows static content
  • Application (for JSM Portal) is offered for every location except the Header
  • Ensure the panel is targeting the correct portal and request types

Panel shows different data to different viewers

  • The panel reads Jira data with the permissions of its Actor; without an actor each viewer sees only what Jira lets them see
  • With Application (for JSM Portal), comments are limited to public ones and attachments to those added by the reporter or to public comments; linked requests are shown only when the customer may see them on the portal
  • See Fields on the portal

Performance

Panels are slow to render

  • Reduce the number of table fields - each field adds to rendering time
  • See Limits for performance recommendations

Too many API calls

  • Each panel that shows linked requests makes API calls to load them
  • Consider combining information into fewer panels rather than many small ones
  • Use Display JQL conditions to prevent unnecessary data loading when the panel wouldn’t be shown

Delegation Issues

Project admin can’t see Customer Portal Fields Panel settings

  1. Verify delegation is enabled for the project - check with a site admin
  2. The setting appears in Project Settings → Apps → Customer Portal Fields Panel settings
  3. The user must have the Administer Projects permission for the project
  4. If using “Disable with Exceptions” policy, the specific project must be in the enabled list

Project admin can’t edit a configuration

  • Project admins can only edit configurations that target their specific project
  • Configurations targeting “All Projects” or multiple projects are managed by site admins only
  • The Actor setting cannot be changed by project admins