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

[Max Foerster - K15t · Accepted solution]

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

[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 .
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

[Max Foerster - K15t]

I suggest thinking through your whole JQL clause again. Maybe it doesn't make sense, and that's why it does not return any issues:

• Issues that have been created in the past seven days
• Are in status (Done, "Forced Close", "In Progress", "On Engineering", "Reporter validation", "Waiting for reporter")
• Have a resolution value of "Done, "Won't Do", Duplicate, Declined)" <- I think that's where it happens. You look for statuses that, to me at least, don't sound like they have a resolution value set, like "In Progress" or "Waiting for reporter". That's potentially what breaks your logic.
• Have a specific assignee set
• And the SLA has run for more than 4 hours

[Harrica Rion]

Hi Max,

Sorry for the late reply.
Thank you for the detail.

I just tried what you said. I try to delete "Resolution" to give more wide filter.
But unfortunately its not works.

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

Thank you

[Max Foerster - K15t]

Hey @Harrica Rion, now it seems that you're looking for the exact "2h" elapsed instead of a minimum of two hours (>=). A general comment on what you're trying to achieve here. Let's think about it as a funnel. Is it something that can actually return issues, or is it more of a filter for you that should alert you about issues that have been missed?

• How many tickets are created during these 7 days?
• How many of them meet the SLA criteria
• How many of them are in the specified statuses
• How many of them are assigned to the specific users

The next thing that comes to my mind is, does the assignee change? Could it be that they are not the assignee anymore, so "was" makes more sense?

[Harrica Rion]

Hi Max,

Ah I'm sorry its my mistakes. I copied wrong script. Sorry.
Before I use "Time to resolution" = elapsed("4h") its for SLA + 2h .

For more clear what I want to achieve are :
1. How many tickets that elapsed SLA + hours and with filter ticket are created during these 7 days.
2. For Assignee yes I need to filter that assignee. but, let me try without using that asignee.

Thank you Max

[Max Foerster - K15t]

Hey @Harrica Rion ,

"Time to resolution" = elapsed("4h") won't get you far. You will have to use >=. We talked about this before. 😄

[Harrica Rion]

Hi Max,

Ah I see, sorry my mistake for this.
Thank you So much Max.

Let me try.

[Harrica Rion]

Hi Max,

Thank you its work now.
Thank you so much for your help. 

[Max Foerster - K15t]

I'm happy to hear! Please consider accepting my answer, so your question is marked as resolved to the community. :)

Best, Max