JQL Searching

Required knowledge

This page requires some knowledge of searching for issues using JQL. It has been described in the original Atlassian documentation. Please click here to get more information on querying for issues. Due to the Issue Navigator limitations, it's not possible to search for the SLAs in the Basic mode.

SLA PowerBox for JIRA provides a set of functions you can use to track performance against your SLAs. This page lists the SLA-specific JQL functions you can use to query the SLA data in your issues, as well as some examples of creating common JQL, queries on SLA Metrics.

Table of Contents

Search functions

You can search for issues with 11 different functions that allow you to search against three different types of functions:

  • SLA Metric State - returns issues whose SLA currently has a specified state.
  • SLA Breach Status - gets issues whose SLA is currently breached or not breached.
  • Metric's Duration - examines issues against their SLA Metric's time condition.

Function TypeFunctionDescriptionExample

SLA Metric State

isActive()When used with "="  the operator shows only issues with SLA Metric active (counting time). When used with "!=" the operator returns only issues having SLA in any other state."Time to Resolution" = isActive()
isOnHold()Shows only issues that have SLA paused when used with "=" the operator."Time to Resolution" = isOnHold()


Displays issues whose SLA is cancelled."Time to Resolution" = isCanceled()


Returns only issues whose SLA Metric is already fihished (the calculation is over)."Time to Resolution" = isFinished()


Shows only issues whose SLA Metric has not started yet (but has a valid SLA Agreement)."Time to Resolution" = isNotStarted()

NEW IN VERSION 3.2.3Returns only issues whose SLA Metric state was last updated after or before the specified date

"Time to Resolution" > stateUpdated("-10h")
Breach statusslaBreached()Returns only issues whose SLA Metric is already breached (regardless of its state). When used with "!=" the operator shows only not breached SLAs."Time to Resolution" = slaBreached()

startDate()Gets issues whose SLA Metric has started after or before a specific date.

"Time to Resolution" <=  startDate("2016-12-01")

timeElapsed()Displays issues whose SLA Metric matches a given condition on elapsed time since the start only.

"Time to Resolution" > timeElapsed("3h 20m")


Gets issues whose SLA time is over at a specific time from now. It doesn't check the SLA calendar's off-time."Time to Resolution" >= timeEndsWithIn("30m")


Displays issues whose SLA Metric meets condition on the remaining time before SLA breaches. It takes into account the calendar's off-time."Time to Resolution" < timeRemaining("1h")


Gets issues whose SLA Metric's remaining time by percent meets a given condition. Accepts only the following percent values: 10, 20, 25, 30, 40, 50, 60, 70, 75, 80 and 90."Time to Resolution" > timeRemainingInPercent("80")

Each function listed above checks only one parameter and searches for the current Metric's data. Historical cycles are not searchable (e.g. you can not search for issues that have been paused in the past, but are currently active).


Usually, you need to query for more than one function to get reasonable results.

  • Example 1: Get issues with "Time to Workaround" which will be breached in the next 30 minutes and its time is being counted down.
"Time to Workaround" = isActive() and "Time to Workaround" <= timeEndsWithIn("30m")

  • Example 2: Get issues whose "Time to Analysis" has been breached and they are still neither finished nor canceled.
"Time to Analysis" = slaBreached() and "Time to Analysis" != isFinished() and "Time to Analysis" != isCanceled()