Customize VIEW26 Portal Reports | Charts and Reports for JSM

Give customers useful ways to explore a shared report while keeping the report owner’s saved filters and request access rules in place. Jira administrators can offer common filters to everyone or add extra fields for selected organizations and reports.

Choose the right configuration

Use	Configure	Customers receive
Common filters, such as Status or Issue Type	Portal Filters	Default fields on every report for every organization.
A customer-specific field, such as a customer category	Filter groups	Extra fields only when the organization and report match the group.

Default fields and filter groups are additive. Customers receive the default fields plus fields from matching groups. To limit a field to particular customers, keep it out of the global Portal Filters list.

Open the Customer Portal settings

Sign in to Jira as an administrator.
Open Jira admin settings → Marketplace apps → Charts and Reports → Settings.
Select Customization → Customer Portal.

Set default Portal Filters

Under Portal Filters, select Select Fields. Search for and choose an available field.
Repeat for each field that all customers should be able to use. The selected fields appear below the selector.
Changes to this default list are saved automatically. To remove a field, use the remove icon on its selected field.

Default fields are offered to every organization on every shared report. Adding a field through More Filters in an agent View does not add it to this customer list. Choose from the fields offered by the selector; not every Jira field is supported.

Under Filter groups, select + New filter group.
Enter a descriptive Name, such as Customer A – support filters.
Under Filters, add the fields these customers need.
Under Organizations, choose one or more organizations. Use All organizations (also customers with no organization) only when the fields should be available to everyone.
Under Reports, choose one or more reports, or select All reports shared with these organizations.
Review the selected organizations and reports, check any field-value warnings, and select Save group.

A filter group never shares a report. First share the View with the relevant organization using the report’s Share dialog. Choosing All reports includes only reports already shared with those customers.

Use separate groups when customers need different fields on the same report. For example, share a Support Overview report with Customer A and Customer B, then create one group for Customer A with Product Area and another for Customer B with Region. Keep Status and Issue Type as defaults if both customers need them. The report can stay shared with both organizations while each gets its own additional fields.

Preview and maintain the configuration

Under Preview as a customer, choose an Organization and a Report.
Review the effective fields and where each field comes from: Default or a matching filter group. A report-not-shared message means the organization cannot open that report.
Use Edit on a group to change its name, fields, organizations or reports, then select Save group.
Use Delete to remove a group you no longer need. Customers lose that group’s fields the next time they open a report.

Removing a field from one group does not hide it if it is still a default field or is supplied by another matching group. After changing configuration, reopen the customer report to load the updated field list.

Understand request access and filter values

Customer filters can narrow results within the report owner’s saved filters; they cannot widen the report beyond that saved scope.
Filter groups control which fields are offered. They do not add organization membership, share a View, or grant access to more requests.
For fields whose choices are derived from requests, group values come from requests in the group’s organizations. Review the organization scope before including a confidential field.

Some fields, such as Priority, Fix versions and Request Type, can list values from Jira configuration rather than only values found on those organizations’ requests. Read the warning shown for each selected field. Do not assume every dropdown contains only organization-specific values.

If a field or filter is missing

Check both the default list and filter groups. Confirm the group includes the customer’s organization and the report they opened.
Confirm the report is shared with the organization; a filter group alone does not give access.
For a missing custom field, check Settings → Data Sync & Projects → Projects → Fields and include it in the app’s synced fields.
Use a field offered by the selector, then reopen the portal report after configuration changes.

Configuration example

The configuration screen below shows default fields at the top and organization/report filter groups underneath. Names shown are examples from a test site.