...
...
...
...
...
| Button handy |
|---|
...
| id | k6bthk4se78 |
|---|---|
| title | TTS |
| alignment | left |
...
|
...
|
...
|
...
|
...
|
...
|
...
| Button handy |
|---|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This page is about Time to SLA for Jira Cloud. Using Jira ServerOn-Prem? Click the Server On-Prem button above. |
This page contains step-by-step instructions on how to create an SLA on Time to SLA for Jira Cloud.
...
Log in to your Jira Cloud account.
...
Click Apps in the header menu and open the Time to SLA app.
...
From the header menu, go to
...
SLAs.
...
Click Add New SLA Definition and the SLA configuration screen will appear.
...
In our example, we’ll set up an SLA for First response time. Follow the example through the screenshots below, and jump between different steps with one click by using the list below:
...
Anchor icon-link icon-link
...
icon – Here, create a name for your SLA.
...
Anchor enable-sla enable-sla
...
Enable SLA – Enable or disable your SLA. When this toggle is disabled, all SLA ions will be stopped. The SLA will not appear in fields, reports, and other configurations. Enabling it will do the opposite.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Why would you disable an SLA? When you disable an SLA, it is taken off your list of issues without deleting its settings, which could be useful in many situations. For example: You could want to hide some SLAs that are irrelevant to your workflow but might be needed in the future. As a result, you wouldn’t want to lose the configurations. In this case, disabling those SLAs could do the trick. |
Anchor SLA-Scope SLA-Scope
...
SLA Scope – This section allows you to define the Projects, Issues (JQL), and Workflows that an SLA will be applied to. Use these to limit your issues.
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Note | ||||||||
We recommend you fill out at least 1of these fields. It is not necessary to fill out all of them. |
Anchor Conditions Conditions
...
Conditions – Set your SLA conditions here. There are 4 conditions: START, END, RESET, and PAUSE ON. START and END are mandatory, while RESET and PAUSE ON are not. Which of these to use depends on your use case.
See below for what a “First response time” SLA’s conditions may look like:
...
You can add more than one condition. Keep in mind that there is an OR function between conditions, which means when any of the conditions are met, the SLA will trigger.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Learn more about SLA Conditions here. |
Anchor Goals Goals
...
Goals – Set your SLA goals. Goal selection is a two-step process: first, the goal type; then, the goal itself. There is always one goal by default, but this can be disabled.
...
You can add numerous goals by using the Add new SLA goal button. All goals, except the default goal, have to include a JQL or a priority.
...
...
The goal types are:
Negotiation date
Dynamic duration
Duration
Next business day
No target
To learn more about them, check out the SLA Goals page.
Anchor Calculation-Method Calculation-Method
...
Calculation Method – Select the ion method for the elapsed duration. Your options are All Cycles, First Cycle, Largest Span, and Last Cycle.
...
For example, if the SLA starts with an Open status and ends with a Resolved status, the All Cycles method will add up all the cycles between Open and Resolved statuses.
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Display linked issues' SLAs – If you choose this option, you’ll be able to display the SLAs of all linked issues related to the link types selected in the issue, which means you need to create another SLA definition for the project. Here choose inward link types (i.e., blocked by, cloned by, etc.) for the linked issue.
...
To better understand how this function works, let’s explore an example:
Assume there are two issues: Issue 1 in "Project 1" and Issue 2 in "Project 2". The link created between these issues is as follows:
"Issue 1 blocked by Issue 2" hence "Issue 2 blocks Issue 1 ". The SLA configuration only has "Project 1" defined for the SLA scope Projects and is configured to display Linked Issues Blocks.
With this configuration, the expectation is that you should be able to see the SLA of the linked issue "Issue 1" on "Issue 2".
| Anchor | ||||
|---|---|---|---|---|
|
...
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||