Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This information can be used as a self-learning resource to understand who an ideal customer fit is and the value-add that Advanced Portal Reports brings to your customers.

Table of Contents
stylenone

Target Audience

Advanced Portal Reports is build for companies using Jira Service management who need to support more complex scenarios of Portal usage. Advanced Portal Reports works well for companies of any size - both small entities and enterprise customers use it to deliver better visibility into Jira’s data at the Portal.

Key use cases

Add a

fieldAdd a field:

custom/ standard fields to the Portal

A company uses JSM to manage customer requests. They have extended Jira with standard and custom fields and need to be expose these fields in the Portal. Portal users should be able to view and search by these fields.

Using Advanced Portal Reports you can add a standard or custom field field on the Portal

  • on request’s page

  • as a column in request list

  • as a search

Send this … documentation to end users
  • filter

See supported fields here.

🙏 Needs:

  • Ability to view and search on the Portal information stored in custom fields

🫤 Pain points:

  • Lack of custom fields as columns in the Portal

  • Lack of custom fields on request page Wasting time to get needed information via other channel/ processRequest page

Find requests by ID

🙏 Needs:

  • Ability to search by custom field

  • Ability to show a custom field on request page

🫤 Pain points:

  • Lack of custom fields as columns

  • Lack of searching by custom field

  • Wasting time in scrolling pages to find requests

Sorted lists

🙏 Needs:

  • Ability to order the request’s list based on a field such as priority or any other standard or custom field

🫤 Pain points:

  • Lack of custom fields as columns

  • Lack of sorting in portal

  • Wasting time in manual scroll and sort of the list

Visibility to SLA about to breach

🙏 Needs:

  • Ability to monitor the SLAs and be able to undertake preventive actions on time

🫤 Pain points:

  • Lack of SLA fields as columns

  • Lack of SLA fields at request’s page

  • Lack of searching by SLA to breach

  • Wasting time to get needed information via other channel/ process

Text search

Pre-defined filters

Reporting