Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,556,421
Community Members
 
Community Events
184
Community Groups

16 Most Popular JQL Filters for SLAs in Jira Cloud

JQL-filter-vs-SLA-Time-and-Report-for-Jira.pngAs a Jira user, you're likely familiar with Jira's Service Level Agreements (SLAs) and how they can help teams track and improve their service delivery. However, finding the correct information within Jira can take time, especially when dealing with hundreds or even thousands of issues.

That's where Jira Query Language (JQL) comes in. With the right JQL queries, you can identify issues that have breached their SLAs, monitor SLA metrics, and more.

In this article, we'll go over 16 of the most popular JQL queries for SLAs in Jira. Whether you're a Jira administrator, team lead, or just a curious user, these queries will help you get the most out of Jira's SLA features.

🧐 Now, without further ado, let's look at the most popular JQL queries for SLAs:

  • Find all issues in specific Project where the SLA goal has been breached:
    project = <Project name> and "Time to resolution" = breached()
  • Find all issues where the SLA goal has not been breached:
    "Time to resolution" != breached()
  • Find all issues where the time remaining to meet the SLA goal is more or less and equal or not equal to a specific value:
    "Time to resolution" <= X

    "Time to resolution" >= X

    "Time to resolution" = X

    "Time to resolution" != X
    (replace "X" with the desired value)
  • Find all issues where the SLA goal has been paused:
    "Time to resolution" = paused()
  • Find all issues where the SLA goal has been achieved:
    resolution is not EMPTY
  • Find all issues that have an SLA that is about to breach within the next X hours:
     project = "Project Name" AND status != "Closed" AND "Time to resolution" <= remaining("X")
  • Find all issues where a specific user has breached the SLA goal:
    "Time to resolution" = breached() AND assignee = "User Name"
  • Find all issues where the SLA goal has been breached after a specific date:
    project = <Project name> AND  "Time to resolution" = everBreached() AND status changed BY <User ID> AND status changed TO Done AFTER 'YYYY/MM/DD'
  • Find all issues where the time remaining to meet the SLA goal is between two specific values:
    "Time to resolution" >= X AND "Time to resolution" <= Y (replace "X" and "Y" with the desired values)
  • Find all issues that are currently unresolved and assigned to the current user:
    assignee = currentUser() AND status != Resolved AND status != Closed
  • Find all issues that were resolved within a specific date range:
    resolutiondate >= "YYYY/MM/DD" AND resolutiondate <= "YYYY/MM/DD"
  • Find issues with a specific status when the SLA is exceeded:
    project = <Project name> and priority=<your priority> and "Time to Resolution" = breached()
  • Find issues with breached SLAs in JSM for email subscription:
    "Time to Resolution" <= remaining("0m") and "Time to Resolution" > remaining("-60m")

These 16 JQL queries are just the tip of the iceberg when it comes to SLA monitoring in Jira. And honestly, it was not easy for me (not a JQL person) to ensure that all of these JQLs were running correctly. Furthermore, a user question about "what JQL I should use for xxx" is one of the most popular themes in the Atlassian Community, so what about doing work a little simpler?

Allow me to introduce one of the third-party apps for Jira Cloud — the SLA Time and Report add-on. 

sla-time-and-report-add-on-for-jira-cloud.gif

Using JQL and the Jira SLA reporting app, you can monitor SLAs in real-time and generate detailed SLA reports for your team and stakeholders. We hope these JQL queries and our add-on will help you achieve your SLA goals and improve your team's productivity. 

If you're interested in exploring other time-saving add-ons, such as for Jira business process management, be sure to check out the Atlassian Marketplace. All add-ons by SaaSJet have a trial, so take advantage of the opportunity to try them.

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events