The information in this page can be used to quickly see the main use cases that can be implemented with Advanced Portal Reports. It shows the main features into perspective of specific requirements. Use cases are complemented with a lot of screen shots - to help you quickly grasp them.
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 Features
1️⃣ Advanced Requests Report
Using Advanced Requests Report the Portal can be extended to show needed fields on request’s page and requests list.
In the requests lists Customers can:
view additional fields (standard and custom). See APR Supported Fields.
save filters as saved views
export requests as csv or excel
2️⃣ Created vs Resolved chart
Using Created vs Resolved chart customers can analyze the speed of creating requests vs the speed of completing requests. By comparing the number of issues created with the number of issues resolved, users get insights into whether the support team is able to handle the volume of incoming work effectively.
Administrators can:
save filters as global views, so that customers can directly start using them
control which for projects is enabled “Advanced Portal Reports”
control the “access point” and its text
control which fields to be added, and their order as columns
control access to advanced features
For more configuration details see the documentation - https://tools4teams.atlassian.net/wiki/spaces/APRFJSM/pages/1507885092/Configure+Advanced+Portal+Reports
🫤 Pain points
Pain points which Advanced Portal Reports address:
Portal is too limited and can not be customized to show custom fields on request’s page
Portal is too limited and can not be customized to show custom fields ad columns on requests list
Portal lack needed features to work with requests such as - filter, sort, export
Portal lack reporting and features allowing customers to analyze the performance
Key use cases
Exposing SLA fields to Portal customers
🙏 Needs:
One common use case of Advanced Requests Report аdvanced Portal Reports is to show SLA fields on the Portal. Usually companies want to expose fields such as “Time to first response” and “Time to resolution” at the Portal and allow customers to view, search and sort by SLA fields.
🫤 Pain points:
Lack of ability to view a SLA on request’s page
Lack of ability to view a SLA as a column in request list
Lack of ability to filter by SLA the request list
Lack of ability to sort by SLA the request list
Solution:
Using Advanced Requests Report аdvanced Portal Reports the Portal may be extended to show SLA fields in both locations - request’s page and requests list.
This will enable Customers to view the SLAs at both on request’s page and in the requests lists - where they could sort the requests list by SLA and use it as a filter.
See full list of supporter fields here - APR Supported Fields
SLA on request’s page
SLA as column and filter in requests list
Extending Portal with powerful search
🙏 Needs:
In some cases customers need to be able to search by values stored somewhere in a text fields. For example a text in the description, or a value stored in custom text fields such as “External Reference ID” custom field. They want to be able to do exact match and partial match. In other cases customer need to be able to search by reporter, by custom field or SLA.
🫤 Pain points:
Limited ability to search for requests on the Portal
Solution:
Using Advanced Requests Report customers can search requests:
by text (JQL text~). By default the search result returns both exact and partial matches in any text field. Text search is limited by the functionalities of the underlying Jira and JQL. For more information refer to the documentation - https://tools4teams.atlassian.net/wiki/spaces/APRFJSM/pages/1545109693/Search+for+requests
by SLA
by custom fields added as columns - see here more details https://tools4teams.atlassian.net/wiki/spaces/APRFJSM/pages/1509097598/Filtering
See below few search screens.
Speed JSM adoption with pre-configured projects - fields, columns and filters
🙏 Needs:
pre-defined tables = project B = use other fields
Company uses JSM to track support requests related to their Web sites. They have extended Jira with the following fields:
“Web site” = drop-down to select impacted site
“Category”
“Revised Priority”
Customers create tickets in the same JSM project.
The admin have configured project “Web Site Support”
Reference (Key)
Summary
Assignee
Status
Priority
“Web site” = drop-down to select impacted site
“Category” = in which category falls the request
“Revised Priority” = after internal review of the priority
The admin have configured project “Feature Requests”
Reference (Key)
Summary
Priority
Status
Sprint/Release
Environment
Resolution
The admin have configured project “Feature Requests”
Reference (Key)
Request Type
Reporter
Type of system
Error Number
Summary
Assignee
wants to provide visibility to Open Incidents to their customers, so that customers are aware of current status of systems.
Global view “Open Incidents of Key systems” + custom field “asset” = which system + SLA + linked issues/ planned fix ?
Columns:
Key
Summary
Affected System (Asset)
SLA
Linked Issues
All requests that I have permission to view
🫤 Pain points:
Limited ability to search for requests on the Portal
Solution:
Using Advanced Requests Report аdvanced Portal Reports customers can search requests:
by text (JQL text~). By default the search result returns both exact and partial matches in any text field. Text search is limited by the functionalities of the underlying Jira and JQL. For more information refer to the