/
Generating Incident Summary Report with data from ServiceNow

Generating Incident Summary Report with data from ServiceNow

The purpose of this document is to define the use case for generating an Incident Summary Report in Visionade using the pivot table feature. This report allows users to analyze the number of incidents in ServiceNow based on their State and Priority, helping them gain insights into incident trends over a specific period.

Introduction

Visionade provides an interactive pivot table feature that enables users to organize and analyze ServiceNow incident data efficiently. By configuring the pivot table settings, users can categorize incidents by State and Priority, count the number of incidents, and apply date filters for a specified timeframe. Additionally, a Pie Chart visualization enhances the data representation, making it easier to interpret the distribution of incidents.

Prerequisites

  • Users have the necessary permissions to configure data sources and reports in Visionade.

  • A connected ServiceNow instance with incident data.

  • Availability of State, Priority, Number, and Opened At fields in the dataset.

Post-condition

  • The Incident Summary Report is successfully generated in Visionade and displayed on the Jira Dashboard.

  • Users can analyze the distribution of incidents based on State and Priority.

  • Connected data source (from ServiceNow) is saved in Data Sources list.

  • Configured report is saved in Reports list.

Use Case Flow Diagram

Step-by-Step Implementation

1. Connect Data Source from ServiceNow

Actions

Actions

1

Click Add Data Source button

image-20250313-091120.png
2

Select “ServiceNow” and click Next

image-20250326-100845.png
3

Fill in validate information and click Save

You can also click Test connection to check the connection before.

image-20250326-101018.png

2. Configure Incident Summary Report

Actions

Actions

1

Click Reports tab

Click Create Report button

image-20250313-093535.png
2

Fill in Name and click Create button

image-20250326-101703.png
3

Click on the Source section

Select “ServiceNow source” as data source

image-20250326-102028.png
4

Click on Table field, and select “Incidents”

image-20250326-102326.png
5

Drag dimension State to section Rows to view incident states as row headers

image-20250326-103450.png
6

Continue to drag dimension Priority to section Columns to view priority as column headers

image-20250326-103321.png
7

Drag dimension Number to section Values and select Count in Aggregation field to view number of incidents in each field of the table

image-20250326-103544.png
image-20250326-103703.png
8

Drag dimension Opened At to dimension Filters to filter incidents opened in Q1 2025

image-20250326-103812.png
9

Click in Filter By field

image-20250326-103907.png

Select condition Is between

image-20250322-095101.png

Enter “1/1/2025” and “3/31/2025” in fields

image-20250322-095206.png

Click OK to filter

10

Select Pie Chart in section Visualization

image-20250326-105003.png
11

Click Save changes to save report

image-20250326-105446.png

3. Add Incident Summary Report to Jira Dashboard

Actions

Actions

1

Open Dashboards screen and click Create dashboard button

image-20250313-111751.png
2

Fill in Name and click Save

image-20250326-110035.png
3

Click Edit button to edit the dashboard

Search “Visionade” to search gadget

Click Add button on Visionade Report gadget

image-20250326-110238.png
4

Select Incident Summary Report

image-20250326-110344.png
5

Click Change layout and select One column

image-20250326-110535.png
6

Click Done to save dashboard

image-20250326-110628.png

4. Result

Report is displayed on Jira Dashboard.

image-20250326-110746.png

Conclusion

With Visionade’s pivot table feature, you can effortlessly analyze ServiceNow incident data to identify trends and patterns. Applying date filters and visualizing data with a Pie Chart simplifies decision-making and streamlines incident management. This report empowers your team with valuable insights to enhance response and resolution efforts.

Other Use Cases In The Future

For more information - check following blogs

Visionade can play a role in providing an overview.

Some of the ideas generated by ChatGPT here

One of the most interesting use cases is

  • Identify spikes in incidents that may correlate with software deployments or infrastructure changes.

Other examples

  1. Incident and Issue Volume Over Time – Trends in reported incidents and issues.

  2. SLA Compliance Over Time – Percentage of incidents and issues resolved within SLA.

  3. Escalation Rate – Percentage of ServiceNow incidents escalated to Jira.

  4. Resolution Time by Severity – Average time taken to resolve incidents/issues categorized by severity.

  5. Deployment Impact on Incidents – Comparison of incident volume before and after deployments.

Incident and Issue Volume Over Time

Graph Type: Line Chart

Purpose:

  • Track trends in the number of incidents (ServiceNow) and issues (Jira) over time.

  • Identify spikes in incidents that may correlate with software deployments or infrastructure changes.

 

Incident Severity vs. Resolution Time

Graph Type: Scatter Plot

Purpose:

  • Visualize the correlation between incident severity and resolution time.

  • Identify high-severity incidents that took longer than expected to resolve.

 

Escalation Rate

Graph Type: Bar Chart

Purpose:

  • Show the percentage of ServiceNow incidents escalated to Jira.

  • Compare different categories (e.g., infrastructure vs. application-related issues).

 

SLA Compliance (ServiceNow vs. Jira)

Graph Type: Gauge Chart

Purpose:

  • Display the percentage of incidents and issues resolved within SLA.

  • Compare ServiceNow SLA adherence with Jira development resolution times.

 

Open vs. Resolved Tickets (Backlog)

Graph Type: Stacked Bar Chart

Purpose:

  • Compare open vs. resolved ServiceNow incidents and Jira issues.

  • Identify backlog accumulation trends.

 

Average Resolution Time per Category

Graph Type: Box Plot

Purpose:

  • Show how resolution times vary across different incident and issue categories (e.g., hardware, network, application).

  • Identify outliers where issues take significantly longer to resolve.

 

Incident Source Analysis

Graph Type: Pie Chart

Purpose:

  • Display the distribution of ServiceNow incidents by source (e.g., user-reported, monitoring alerts, API triggers).

  • Identify the primary contributors to IT issues.

 

Jira Issue Types Related to Incidents

Graph Type: Horizontal Bar Chart

Purpose:

  • Show which Jira issue types (Bug, Story, Task) are most frequently linked to ServiceNow incidents.

  • Identify areas where better proactive issue resolution could reduce incidents.

 

Deployment Impact on Incidents

Graph Type: Overlayed Line Chart

Purpose:

  • Compare the number of ServiceNow incidents before and after software deployments (from Jira).

  • Identify patterns in post-deployment incident spikes.

 

Assigned vs. Unassigned Tickets

Graph Type: Doughnut Chart

Purpose:

  • Highlight the proportion of incidents/issues that are assigned vs. unassigned.

  • Help prioritize unassigned tickets to prevent delays.

Related content