nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JQL for SLA everbreached()

Harrica Rion

Hi , I have a question regarding filtering issue for my reports.

I want get the data that issue that created 30 days but with SLA everBreached from the SLA time and plus 2 hours.

created >= -30d AND status in (Done, "Forced Close", "In Progress", "On Engineering", "Reporter validation", "Waiting for reporter") AND resolution in (Done, "Won't Do", Duplicate, Declined) AND assignee in (62e6b9955111209f4fddaaa0, 624c0065ad6b7e006aa83708, 6304402c5934bfa83b39e8d7, 6304402da4f57644346ae595, 6226e761a1245000688a314b, 61305e42ae44ae0070c4e5cf, 630d656f3778a7aadf1827e6, 6325734a4395a525a712a904, 6304402b49a5c6754d90a02f) AND "Time to resolution" = everBreached() ORDER BY priority DESC, created ASC

Right now I use this JQL, but i don't get data that I want.
Because it only filter issues that everbreached of SLA time.

I need data with Everbreached SLA + exceed more than 2 hours.

Is it possible to filter it?
Thank you

Accepted answers

Max Foerster - K15t

Hi @Harrica Rion

The function everBreached() does not support time parameters, but one thing comes to my mind that I have never tried. You also have the function elapsed() that supports time parameters. Could you try combining the everBreached function with the elapsed() function and take the amount of time the "Time to resolution" SLA is set to plus 2 hours, e.g., die SLA is set to 8hrs, you try elapsed("10h").

Best, Max

All comments

Max Foerster - K15t

Hi @Harrica Rion

Best, Max

Harrica Rion

Hi Max,

Thank you for reaching me out..
I tried with elapsed. unfortunately its not works.
The data not shown, precisely there"s no data.
I tried using elapsed with my SLA time to try its work or not. but it's not work because they don't found any data.

Max Foerster - K15t

Hey @Harrica Rion

just a minor thing that I missed in my last response, but did you use "Time to resolution" >= elapsed("10h")?

Probably that is the issue here. Unless you have requests that meet the criteria with exactly 10 hours. Then it should work! I tried it in my test instance with some old issues being 500hrs over the SLA... 😄

Best, Max

Harrica Rion

Hi Max,

Yes I tried using that smile .
Bellow, here's the script

created >= -7d AND status in (Done, "Forced Close", "In Progress", "On Engineering", "Reporter validation", "Waiting for reporter") AND resolution in (Done, "Won't Do", Duplicate, Declined) AND assignee in (62e6b9955111209f4fddaaa0, 624c0065ad6b7e006aa83708, 6304402c5934bfa83b39e8d7, 6304402da4f57644346ae595, 6226e761a1245000688a314b, 61305e42ae44ae0070c4e5cf, 630d656f3778a7aadf1827e6, 6325734a4395a525a712a904, 6304402b49a5c6754d90a02f) AND "Time to resolution" >= elapsed("4h") ORDER BY priority DESC, created ASC

Oh, My SLA time are 2 hours. so SLA plus 2 hours , I set it 4h.

Thank you

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management