...
...
| id | k6bthk4se78 |
|---|
| title | TTS |
|---|
| alignment | left |
|---|
...
...
| On-Prem | | link | https://appfire.atlassian.net/wiki/spaces/TTS/pages/46727170/Select+a+Calculation+Method |
|---|
|
...
...
...
...
...
...
...
...
...
...
| link | https://appfire.atlassian.net/wiki/spaces/TTSC/pages/35456295/Select+a+Calculation+Method |
|---|
| width | 84 |
|---|
|
| Panel |
|---|
| panelIconId | atlassian-info |
|---|
| panelIcon | :info: |
|---|
| bgColor | #F4F5F7 |
|---|
|
This page is about Time to SLA for Jira ServerOn-Prem. Using Jira Cloud? Click the Cloud button above. |
...
Now, let’s take a look at the different calculation methods you can choose from.
First Cycle
Last Cycle
All Cycles
Largest Span
Important Notes
1. First Cycle – The First Cycle method calculates only the first cycle between the Open and Resolved statuses.
...
This calculation method considers the date/time when your issue met the first start condition and uses it as the SLA start date. The date/time when your issue met the first end condition is used as the SLA end date.
...
| Panel |
|---|
| panelIconId | 23f2 |
|---|
| panelIcon | :timer: |
|---|
| panelIconText | ⏲️ |
|---|
| bgColor | #FFEBE6#F4F5F7 |
|---|
|
If you want to set up an SLA for First Response Time, you could use the First Cycle method. |
...
2. Last Cycle – The Last Cycle method calculates only the last cycle between Open and Resolved statuses.
...
This calculation method considers the date/time when your issue met the last start condition and uses it as the SLA start date. The date/time when your issue met the last end condition is used as the SLA end date.
...
3. All Cycles – The All Cycles method will add up all cycles between Open and Resolved statuses.
...
This calculation method considers the date/time when your issue met the last start condition and uses it as the SLA start date. The date/time when your issue met the last end condition is used as the SLA end date.
...
| Panel |
|---|
| panelIconId | 1f3c1 |
|---|
| panelIcon | :checkered_flag: |
|---|
| panelIconText | 🏁 |
|---|
| bgColor | #EAE6FF#F4F5F7 |
|---|
|
To give you a better idea, selecting All Cycles for your Time to Resolution SLA would be a logical decision since you'd want to know how many days it took you to solve the issue. The All Cycles method would track the time from the issue’s creation to when it was resolved. |
...
4. Largest Span – The Largest Span method will calculate the elapsed time between the first Open and last Resolved status.
...
This calculation method considers the date/time when your issue met the last start condition and uses it as the SLA start date. The date/time when your issue met the last end condition is used as the SLA end date.
...
| Panel |
|---|
| panelIconId | atlassian-question_mark |
|---|
| panelIcon | :question_mark: |
|---|
| panelIconText | :question_mark: |
|---|
| bgColor | #DEEBFF#F4F5F7 |
|---|
|
You may ask – How is this different from the All Cycles method? Well, unlike the All Cycles method, the Largest Span also includes intermediary statuses. In this case, these are the Resolved/Closed statuses. |
And there you have it! When in doubt, always refer to our work process diagrams, as they can teach you how different methods work in the most concise and efficient way possible.
...
To better understand SLA calculation, check out these important notes:
If you have different business hours for each day (as shown below), TTS will consider Monday’s business hours.
...
For example, if you add a goal as shown below (1d), TTS will consider this 1 day as 10 hours. This is because your business hours add up to 10 hours on Monday.
...
If you want to set your business hours for the “day” option, you can use the Length of Business Day option as shown below:
...
🖇️ Related Articles
| Panel |
|---|
| panelIconId | 1f371 |
|---|
| panelIcon | :bento: |
|---|
| panelIconText | 🍱 |
|---|
| bgColor | #C0B6F2#F4F5F7 |
|---|
|
The Anatomy of an SLA Panel |