How to find issues that the status was changed 3 days after the issue was created

[Samuel Bar]

I will appreciate it if you can advise what should be the right JQL

we have an SLA that Bugs should be handle until 3 days since they were opened.
When a new bug is created the status is "New" the status should change to status "Open", according to the SLA (not more than 3 days since the createdDate)

Something like "status changed TO OPEN AFTER created > "+3d"

Thanks,

Samuel Bar

[Jack Brickey · Accepted solution]

Can you not come at this from a different angle? query for all issues still in New after 3d? You could set this up as a daily subscription and email the team.

status = new and createddate < startofday(3d)

[Samuel Bar]

Thanks @Jack Brickey ,
This is will work perfectly for sending as you mentioned a reminder on a daily base.
I would like also to able to review on a weekly base how many bugs did not achieve the SLA for reporting during a status meeting
Example:
In the last week, 5 new bugs were open and 2 of them did not meet the SLA(not more than 3 days since the createdDate and the status was changed to "Open)

[Jack Brickey]

I don’t believe this is possible OOTB. This is best handled by SLA function and while JSD has this built in JSW does not. There are addons for JSW to present SLA function.

now that I think about it you could do this...

create an automation that runs daily, as above or similar, and add a label or set a custom field value to indicate ‘breach’. Now you can use that label or field to query for breaches.

[Samuel Bar]

Thanks @Jack Brickey !!

[Zoryana Bohutska _SaaSJet_]

Hi @Samuel Bar 

Also, you can consider SLA Time and Report. It lets you set SLA time limit for 3 days and configure automate action for overdue issues as notification, changing assignee, status or priority. This tool works with issues from Jira Core, Jira Sofware and Jira Service Desk.

Hope it helps

Regards

[Gökçe Gürsel {Appfire}]

Hi @Samuel Bar ,

For tracking the progress on your SLAs with reports and various notifier options, I suggest Time to SLA.

With Time to SLA you don't need to set up JQLs to track your SLAs, TTS notifiers (email and Slack) will handle this for you.

As for the overall progress of your SLAs, SLA summary report and detailed report will do nicely.

Let me know if you have more questions.

Cheers,

Gokce