JQL functions (SLA 3.0)

Below is a set of custom JQL functions you can use to query issues based on their SLA status in HelpDesk SLA. Whether you need to find tickets that have already breached their deadlines, are still running, paused, or have completed specific SLA goals, these functions let you build precise filters. Each function takes the SLA field name as its argument (and, where applicable, a comparison operator plus a time value) so you can tailor searches to your exact needs.

As of HelpDesk SLA 3.0.0, all SLA metrics are refreshed in the background—so your JQL functions always return up-to-date results. This makes it easy to create a Jira Filter Subscription using any of the functions (for example, issue in slaRemaining('Resolution Time', '<10m') and have Jira automatically email you whenever your SLAs are at risk of being breached.

slaBreached()

Search for issues with currently breached SLA.

Syntax	slaBreached()
Required argument(s)	field name
Supported fields	SLA 2.0
Examples	find the issues with breached resolution time: `issue in slaBreached('Resolution Time')` find the issues with not breached investigation time `issue not in slaBreached('Investigation')`

slaCompleted()

Search for issues with currently completed SLA.

Syntax	slaCompleted()
Required argument(s)	field name
Supported fields	SLA 2.0
Examples	find the issues with completed resolution time: `issue in slaCompleted('Resolution Time')` find the issues with not completed investigation time `issue not in slaCompleted('Investigation')`

slaElapsed()

Search for issues with particular SLA time spent.

Syntax	slaElapsed( , )
Required argument(s)	field name operator + time (Supported operators: = , != , > , >= , < , <= ) (Time argument format examples: 2h , 2h 45m , 120m)
Supported fields	SLA 2.0
Examples	find the issues with more than 5h 13m of resolution time was already spent: `issue in slaElapsed('Resolution Time', '>5h 13m')` find the issues where elapsed time for the investigation is not 120 minutes: `issue not in slaElapsed('Investigation', '!=120m')`

slaRemaining()

Search for issues with particular SLA time remaining before the SLA is breached.

Syntax	slaRemaining( , )
Required argument(s)	field name operator + time (Supported operators: = , != , > , >= , < , <= ) (Time argument format examples: 2h , 2h 45m , 120m)
Supported fields	SLA 2.0
Examples	find the issues with more than 1h 10m of resolution time remaining: `issue in slaRemaining('Resolution Time', '>1h 10m')` find the issues where the remaining time for investigation is not less than 140 minutes: `issue not in slaRemaining('Investigation', '<140m')`

slaPaused()

Search for issues that have an SLA that is paused due to a condition.

Note that the function doesn't return issues with the SLA time is in progress but on a Calendar pause.

Syntax	slaPaused()
Required argument(s)	field name
Supported fields	SLA 2.0
Examples	find the issues with paused resolution time: `issue in slaPaused('Resolution Time')` find the issues with unpaused investigation time: `issue not in slaPaused('Investigation')`

slaRunning()

Search for issues that have a running SLA, regardless of the calendar.

Syntax	slaRunning()
Required argument(s)	field name
Supported fields	SLA 2.0
Examples	find the issues with running resolution time: `issue in slaRunning('Resolution Time')` find the issues with not running investigation time: `issue not in slaRunning('Investigation')`