This information can be used as a self-learning resource for you and your sales teams to understand who an ideal customer fit is and the value-add that Advanced Portal Reports brings to your customers. The following is highlighted:
Target audience of the product
Customer pain points that it solves
Table of Contents | ||
---|---|---|
|
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 field
Add a field:
on request’s page
as a column
as a search
Send this … documentation to end users.
🙏 Needs:
Ability to view information stored in custom fields
🫤 Pain points:
Need to ask the agent to provide this information as additional step.
Automations may add it as a comment
Lack of custom fields as columns
Lack of custom fields on request page
Wasting time to get needed information via other channel/ process
Find requests by ID
🙏 Needs:
Ability to search by custom field
Ability to show a custom field on request page
🫤 Pain points:
Need to scroll manyLack of custom fields as columns
Lack of searching by custom field
Wasting time in scrolling pages to find requests on the portal
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