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.
| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Panel | ||
|---|---|---|
| ||
Target AudienceAdvanced 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. |
| Panel | ||
|---|---|---|
| ||
Key Features1️⃣ Advanced Requests Report Using Advanced Requests Report the Portal can be extended to show needed fields on request’s page and in a requests list. In the requests lists Customers can:
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. 3️⃣ Administrators can:
For more configuration details see the documentation - https://tools4teams.atlassian.net/wiki/spaces/APRFJSM/pages/1507885092/Configure+Advanced+Portal+Reports |
| Panel | ||
|---|---|---|
| ||
🫤 Pain pointsPain points which Advanced Portal Reports address:
|
Key use cases
| Panel | ||
|---|---|---|
| ||
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
| Panel | ||
|---|---|---|
| ||
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.
| Panel | ||
|---|---|---|
| ||
Extending Portal with Global Views (Pre-configuredJirafilters) |
🙏 Needs:
In certain Jira implementations, the 'FixVersion' field is utilized to track deliveries. For example, a company may expose its JSM Portal to internal business units, allowing them to create change requests. These requests are then planned for implementation using the 'FixVersion' field. To monitor the status of a release, Portal users navigate to the Portal and conduct a search for all tickets associated with a specific release ('FixVersion'). However, users must repeat this search each time they wish to view the status of a release.
By enhancing the portal with Advanced Portal Reports, users can save their filter and reuse it to easily check the status of a release.
The portal users can export the list and use it for UAT preparation. If they have questions in regards to the implementation they can see the assignee.
🫤 Pain points:
Wasting time on repetitive searches
Solution:
To meet customer’s needs the administrator have used Advanced Requests Report.
1) Configured the Advanced Requests Report to show FixVersion as column in the request’s list.
2) Configured Requests View to show FixVersion field on requests page.
3) Created a Global View showing all requests which will be delivered with Q1 release. To create the global view the administrator opened Advanced Requests Report and filtered the table by “FixVersion” = Q1, then saved this filter as a global view “Release Q1 2024”. Once created by the administrator a global view becomes available to all customers in this JSM project.
