| Button handy |
|---|
| blank | false |
|---|
| color | #0052CC |
|---|
| name | Cloud |
|---|
| link | https://appfire.atlassian.net/wiki/spaces/TTSC/pages/48529969/Defining+an+SLA+Calculation+Scope |
|---|
| width | 84 |
|---|
|
| Button handy |
|---|
| blank | false |
|---|
| color | #EBECF0 |
|---|
| name | On-Prem |
|---|
| link | https://appfire.atlassian.net/wiki/spaces/TTS/pages/48334013/Defining+an+SLA+Calculation+Scope |
|---|
| width | 8485 |
|---|
|
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #F4F5F7 |
|---|
|
This page is about Time to SLA for Jira Cloud. Using Jira ServerOn-Prem? Click the Server On-Prem button above. |
The Time to SLA add-on listens to all issue events and recalculates SLAs at each issue event, providing consistency across all issues for all SLAs. However, some projects or issue types may never require SLAs, so it may be a good idea to completely exclude these from the SLA calculation rather than eliminate them with JQL in each SLA definition.
...