Hi Again!
Do you need a JQL to get the time to resolution of each work item?
That should be "Time to resolution." However, this can change because other apps create the same field with the same name.
Example:
project = PROJECTHERE and "Time to resolution" = breached()
will show you all the work items where the SLA has been breached.
This only works for JSM projects.
Don't forget to add the column Time to resolution to see the actual number.
Regards - Aaron
Alrightyy,
But if I want it to show the remaining time before it breaches ?
So sorry, learning JQL, so lots of questions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi!
Here is an example:
Here you see a newly created work item and another one breached.
I haven't added anything else to the JQL. That shows that my current SLA is 16 hrs.
With that, you can create a JQL showing work items with time to resolution lower than, let's say, 6 hours?
> But if I want it to show the remaining time before it breaches ?
The best way to do this is with an automation. You can send a notification when the SLA reaches a certain point.
This is a good doc on how to do that:
Let us know if that works!
Regards - Aaron
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Jeniffer Kamaraj
I understand that Jira's built-in JQL does not allow filtering based on SLA fields like “Time to Resolution”. If you're looking for a way to analyze or replicate resolution time metrics outside the SLA framework or JQL, I can recommend Timepiece - Time in Status for Jira, the oldest and leading "Time in Status" app in Atlassian Marketplace, developed by my team at OBSS. It is available for Jira Cloud, Server, and Data Center.
Timepiece allows you to measure how much time each issue spent in each status or under each assignee — using Jira issue history directly. This makes it a great alternative when you're unable to query SLA durations through native JQL.
To track resolution time specifically, you can use:
Status Duration Report: to view how long each issue stayed in each status
Consolidated Column: to group resolution-related statuses (e.g. “In Progress”, “Escalated”, “Waiting for Support”) under a single custom “Time to Resolution” column
Transition Time Report: to directly measure the time between “Created” and “Resolved” transitions
For all numeric reports, you can calculate averages and sums grouped by any issue field: assignee, project, issue type, request type, or even by date parts (created month, week, etc.).
The app calculates its reports using already existing Jira issue histories no workflow changes or configurations are needed. You’ll be able to report on past issues right after installation.
Timepiece reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. Reports can be exported in various formats, and you can also fetch them via REST API.
Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can help you replicate and go beyond SLA metrics like “Time to Resolution”.
Hope it helps!
Best
Ayça
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.