write JQL to list down tickets in which resolution time is more than 72 hours

[Shirish]

Hello I want to sort out JIRA tickets in which Technical resolution all ticket greater than 72 hours. I tried with below Query.

project in (ISV, OMV, MCS) AND created >= startOfDay(-90d) AND "Task Category" = "Project support" AND resolutiondate not in (-72h)

[Valeriia_Havrylenko_SaaSJet]

Hello @Shirish 👋 

Try to use this: "Time to resolution" <= -72h

Also I will be glad if my article about JQL helps you with this question. 

As an alternative , I guess you can try Time in Status for Jira Cloud (developed by my SaaSJet team) with 7 types of status time reports. 

For example The Time in status report shows how long an issue has been spent in each status.

Add-on has a 30-day free trial version and free up to 10 users. 
Please, let me know if you have any questions

Hope it helps 😌
Valeriia

[Anthony Morais]

Hi @Shirish 

Welcome to the Atlassian Community!!!

Time to resolution >= -72h and project in (ISV, OMV, MCS)

Do not copy and paste otherwise it will give an error, type Time and when the ID appears you select it, see the example below:

 

I hope it helps!

Anthony

[Shirish]

Hello Thanks for your help but output is not as expected. 

I need the tickets which have taken more than 72 hrs for resolution.

I am not getting the expected results. PFA screenshot. In this query tickets which are not breached are also include look at the OMV-2593.

[Kseniia Trushnikova]

Hi @Shirish,

Try to use this: "Time to resolution" <= -72h

[Danut M _StonikByte_]

Hi @Shirish,

As an alternative the JQL, you could also use the Control Chart gadget offered by our Great Gadgets app. It can displays the issue by their resolution time and allows you to set a threshold (like 72h hours) so that the issue that took longer will be displayed in red-color. Like in this example: 

With this app you can easily track many charts and metrics specific to JSM. Just have a look over this article on our blog: An effective dashboard for Service Desk and Customer Support teams in Jira Service Management. 

Regards,

Danut M. 

[Shirish]

I am looking output with JQL only at this time. Could you please help.

[Mehmet A _Bloompeak_]

Hi @Shirish

To get resolution time, you can use lead time (the time interval between the moment an issue is requested to the moment it is completed) reports. For lead time reports, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app. For your case, you can have a look at Lead Time for Each Issue report.

For more detail, you can have a look at Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters article and Status Time Reports How to Videos.

If you are looking for a completely free solution, you can try the limited version Status Time Free.

Hope it helps.

[Emre Toptancı _OBSS_]

Hello @Shirish

Unfortunately, you can't have this report with plain JQL. JQL queries can filter issues but can't calculate resolution times.

The "resolutiondate not in (-72h)" clause in your query filters issues where the resolution date (which is the date when the issue was resolved) is not in the last 72 hours. It doesn't actually do anything about calculating the resolution time. 

To get resolution times, you need to use a marketplace app.

Our team at OBSS built Time in Status exactly for this. It is available for Jira Server, Cloud, and Data Center.  

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. It can also filter issues based on these times.

   

You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. You can use the "Filter" option to filter issues that have a longer/shorter time than a given threshold

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend. 

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

  

https://marketplace.atlassian.com/apps/1211756/

EmreT