|
Hour interval for Time first response
|
|
2
|
51
|
July 17, 2024
|
|
TimetoSLA - Add completed and running cylce
|
|
3
|
75
|
June 26, 2024
|
|
Time domain appears to occasionally lose numerical SLA breach status
|
|
4
|
86
|
May 14, 2024
|
|
How to create a dashboard to show incidents about to miss SLA?
|
|
2
|
156
|
February 29, 2024
|
|
Resolved date based on the created date
|
|
8
|
2396
|
December 6, 2023
|
|
Eazybi with powerbox sla
|
|
2
|
813
|
November 24, 2023
|
|
SLA Report Configuration
|
|
1
|
225
|
November 7, 2023
|
|
Wrong Issue SLA Due Date
|
|
1
|
416
|
April 21, 2023
|
|
SLA count for tickets created in date range
|
|
3
|
1056
|
November 16, 2022
|
|
SLA hours after breach
|
|
4
|
1493
|
August 15, 2022
|
|
Are there predefined measured for SLA in Easy BI
|
|
7
|
442
|
July 26, 2022
|
|
How can I calculate the contractual penalties for issues that are in SLA breached?
|
|
10
|
4113
|
July 25, 2022
|
|
New measure for SLA time to resolution breached but status still in progress
|
|
1
|
624
|
March 25, 2022
|
|
Measure SLA less than 0 in all SLA status
|
|
6
|
1294
|
March 4, 2022
|
|
Create a report about "Jira Service Management", can’t find SLA from Dimensions
|
|
2
|
945
|
June 2, 2021
|
|
SLA report breached not matching JQL querry
|
|
3
|
1871
|
April 19, 2021
|
|
% of issues first response met but on a timeline by hour
|
|
5
|
1344
|
March 26, 2021
|
|
Help in writing a request for the report
|
|
1
|
883
|
March 24, 2021
|
|
Count of cases that will breach SLAs in less than 12 hours
|
|
1
|
1819
|
November 25, 2020
|
|
Application availability/outage time report
|
|
3
|
2182
|
April 15, 2020
|
|
SLA remaining interval
|
|
3
|
1321
|
March 31, 2020
|
|
Indicator SLA - major and blocking
|
|
1
|
1017
|
March 10, 2020
|
|
SLA breached in EazyBI vs. JSQL from Service Desk
|
|
2
|
2413
|
February 19, 2020
|