Order issues by SLA
This page is about Time to SLA for Jira Data Center.
Time to SLA allows you to sort issues by SLA attributes in Jira’s Advanced Issue Search. You can order issues based on the following attributes:
Elapsed duration
Remaining duration
Start date
End date
Target date
TTS Custom Field (Start, End, Target)* (only available in Time to SLA 10.9 and later)
Ordering by SLA attributes is useful for identifying issues with approaching deadlines, prioritizing breached SLAs, or reviewing SLA performance.
Prerequisites
Before using SLA ordering functions, ensure the following:
You are using Time to SLA version 9.8 or later.
You are in Advanced Search mode in Jira (ordering by SLA attributes is not available in Basic Search).
If you are upgrading from a version earlier than 9.8, you must reindex issues with SLAs for ordering to function correctly.
Full reindex – Reindexes all issues in Jira.
Background reindex – Allows reindexing without impacting Jira’s performance.
Project reindex – Reindexes only selected projects.
Order issues by SLA attributes in issue search
Go to Issues > Search for Issues.
Switch to Advanced Search mode. (Ordering by SLA attributes is only available in Advanced Search.)
Type your JQL query.
Append the
ORDER BY
clause with any of our order by SLA functions.
Available SLA order functions
Function | Description | Example JQL query |
---|---|---|
| Order SLAs by elapsed duration. |
|
| Orders issues by remaining SLA duration. |
|
| Order SLAs by start date. |
|
| Order SLAs by end date. |
|
| Order SLAs by start date. |
|
Handling multiple active SLAs
If an issue contains multiple SLAs, Time to SLA sorts issues based on the first SLA within each issue:
Ascending order (
ASC
) → Uses the SLA with the shortest duration or earliest date.Descending order (
DESC
) → Uses the SLA with the longest duration or latest date.
For example, if an issue has two SLAs (one ending in 2 hours and another in 5 hours) sorting by ORDER BY slaRemainingDuration ASC
will prioritize the 2-hour SLA for ordering.