This page is about Time to SLA for Jira Server.
This feature is only available for Time to SLA versions after 9.8.
Time to SLA allows you to order issues based on the following SLA attributes:
Elapsed duration
Remaining duration
Start date
End date
Target date
TTS Custom Field (Start, End, Target)*
*Only available in Time to SLA versions 10.9 and later.
Ordering Issues by SLA Attributes in Issue Search
Go to the Issue Navigator from Issues > Search for Issues and then switch to advanced mode.
Order by SLA functionality is only available in advanced search.
Simply type your JQL query and then append the ORDER BY clause with any of our order by SLA functions.
Here is the list of all SLA order functions available:
slaElapsedDuration
Order SLAs by elapsed duration
Example:
project = TIS ORDER BY slaElapsedDuration
slaRemainingDuration
Order SLAs by remaining duration.
Example:
project = TIS ORDER BY slaRemainingDuration
slaStartDate
Order SLAs by start date.
Example:
project = TIS ORDER BY slaStartDate
slaEndDate
Order SLAs by start date.
Example:
project = TIS ORDER BY slaEndDate
slaTargetDate
Order SLAs by start date.
Example:
project = TIS ORDER BY slaTargetDate
What happens when there are multiple active SLAs on the issue?
Each SLA is individually sorted, and then issues are sorted by the first SLA within them. In other terms:
If you are using ascending order, then the SLA with the shortest duration / earliest date in the issue will be used.
If you are using descending order, then the SLA with the longest duration / latest date in the issue will be used.
If you are upgrading from Time to SLA versions before 9.8, you need to reindex issues with SLAs. Please do one of the following:
Full re-index
Background re-index
Project re-index