How to create Response and Resolution SLA Reports in ServiceNow

[@swarnavamseekrishna5011]

Thanks a lot such a nice info

[@InfernusTech]

Thanks for watching! Please like the video and share it with your colleagues as well.

[@kiranlenovo]

Good to know and thank you so much .. has cleared a few things for me

[@InfernusTech]

Thanks for watching. Please share it with your colleagues too so that it will help them get a better understanding of SLAs :)

[@vishnusaivanka8043]

Thank you for the video; it was very helpful. Could you please upload another video demonstrating how to create a dashboard that tracks the total number of P1 tickets that have breached their response and resolution times, as well as the same information for P2, P3, and P4 tickets?

[@InfernusTech]

Thanks for watching! Sure, we can create that video as well.

[@PK-ex6gk]

Nice explanation. This at least gives us a better idea where the data resides and extract it into excel for our further uses. Keep it up. Subscribed!

[@InfernusTech]

Thanks for watching. Stay tuned fore more!

[@pratikn5486]

Very good and detailed explanation!

[@InfernusTech]

Thank you!

[@SimenStaabyKnudsen]

Nice! What is the incident_metric table for the whole task table?

[@InfernusTech]

Thanks for watching! metric_instance is one which could help you. Do check it out.

[@SimenStaabyKnudsen]

@@InfernusTech thanks!

[@sandeepal1]

What if we have multiple response SLA due to reassignment to incidents from one to another queue. How to find a response SLA against an individual queue ?

[@InfernusTech]

When there is reassignment of Incidents in multiple queues, response SLA reporting starts getting complex. One option is to query the task_sla table, put the necessary filters for assignment groups and the SLA definition > Target > response filter. Once that is done you export the data in excel with the desired columns. The inherent problem here is that if you analyse closely the has breached column will be true for many reassigned incidents. The reason is ServiceNow is using the created date of incident as the starting point for response SLA calculation. For example, if the Incident was created on 21 June 8 PM with Windows queue and later reassigned to Network queue on same day 11 PM, if network team member takes it on their name at 11:15 PM it won’t consider the response for Network team as 15 minutes. It’ll consider it as 3 hours 15 minutes. Right from the starting of incident creation to response from Network team member. Best workaround for response SLA reporting in our opinion is to only consider the first response on an Incident as a KPI for response SLA. Use the incident_metric table as shown in the video and include the Updated(mi_sys_updated_on) column from it in your data export. Once exported use the MIN function in excel or something to find the least of the mi_sys_updated_on time for a particular incident. That will be your first response SLA row for the incident.

[@sunjaiyyuvaraaj.D]

How to compare last month open and closed cases in single dashboard with different

[@InfernusTech]

Here are the steps to create a closed and open tickets view on a single dashboard in ServiceNow: First create a report in All > Reports > Create new, for all created tickets in last month by using the filter conditions as Assignment group = group name AND created On Last month. Next create another report in All > Reports > Create new, for all closed tickets in last month by using the filter conditions as Assignment group = group name AND Closed On Last month. Now, in All > Dashboards > New, create a new dashboard with a friendly name and add those two reports on this dashboard. Feel free to comment if you need any further help on this.

[@jaeger1227]

i need graphics of MY OWN response time and resolution time! can somebody help me!??! T_T

[@InfernusTech]

You’d essentially have to put a filter condition for assigned to or inc_assigned_to as your name. Let us know if that helps or you need more info.