This page is about Time to SLA for Jira Server. Using Jira Cloud? Then please click on the "Cloud" button above.

The new era of SLA management is ready with an enhanced configuration, improved performance and brand new design. For more information, please see Next-Gen SLAs (BETA)

Within Time to SLA, you can:

Differentiate SLAs based on priority.
Start/end your SLAs by issue status, date fields or comments.
Set SLA Goals as a duration, date field or dynamic duration.
Narrow down the scope of an SLA by using JQL functions.
Select one of the calculation methods.

On this page, you will learn how to define an SLA.

Go to SLA configuration

Log into your Jira account.
Click on Time to SLA in the header menu to see the TTS menu.
Go to SLA Configuration.

To define an SLA

Select Jira Workflow. By default All Workflows is selected, however, if you want to group SLAs by workflow, change this option.
Click Add New SLA Definition.
The SLA Definition pop-up screen will appear.
Make sure that the toggle button is ACTIVE, otherwise SLA data will not be calculated for the SLA unless it is re-activated.
Create a Name for the SLA.
Select the Priority of the issue.
You can define different SLAs according to priority for the same set of issues.

Select when the SLA will start.

Select Status if the SLA needs to start when an issue moves to one of the chosen statuses.
Select Date Field if the SLA needs to start when a specified date for an issue is reached.
Select Comment if the SLA needs to start when one of the chosen users comments on an issue.

Hint

Find out how to set when the SLA starts

Click here to find out how to set when the SLA starts

Select when the SLA will end.

Select Status if the SLA needs to end when an issue moves to one of the chosen statuses.
Select Date Field if the SLA needs to end on a specified date provided in the chosen date field.
Select Comment if the SLA needs to end when one of the chosen users comments on an issue.

Click here to find out how to set when the SLA e nds

Select SLA Goal.

Select Duration if the SLA Goal is fixed to a set time value for all issues.
Select Negotiation Date if the SLA Goal is a specific date provided in the chosen date field for an issue.
Select Dynamic Duration if the SLA Goal is bespoke to an issue.

Click here to find out how to set SLA Goals

Select a Calendar.
Click here to find out how to create a calendar.

Select a Calculation Method.

Select All Cycles if the SLA needs to count all cycles between the origin and end statuses.
Select First Cycle if the SLA needs to count only the first cycle between the origin and end statuses.
Select Last Cycle if the SLA only needs to count the last cycle between the origin and end statuses.
Select Largest Span if the SLA needs to count the largest interval between the origin and end statuses.

Enter JQL Functions if necessary.
You can add JQL conditions to filter issues that the SLA includes

Please refrain from using clauses like ORDER BY in your JQL conditions.

Tick the Asynchronous Update box if necessary.

We recommend only ticking this box if any field within the SLA's JQL condition might be updated during the workflow transitions. If you enable this option, then Time to SLA will make calculations after issue events occur. You might expect better issue load times but there will be a delay of about one minute before seeing the changes on SLAs.

Adjust the Slider to determine when the color of an SLA will change according to the time remaining on the SLA Goal.
Click Save.
You should now be able to see the SLA on the list.

You will see the JQL icon in the list if you entered some JQL functions.
You will see the RESET icon in the list if you entered some RESET conditions.
You will see the PAUSE icon in the list if you entered some PAUSE statuses.
You will see the icon in the list if you entered some SLA notifiers.