This page is about Time to SLA for Jira On-Prem. Using Jira Cloud? Click the Cloud button above.
On this page, you’ll learn what different calculation methods mean and which one might be the best for your use case. The calculation method you select impacts how Time to SLA will calculate the elapsed duration of your SLAs.
Before you begin: Each interval between a consecutive SLA start and end point within an issue's lifespan is defined as a cycle. By default, each cycle starts with the earliest start point and the earliest end point.
Now, let’s take a look at the different calculation methods you can choose from.
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.
Important: After meeting the first end condition, your SLA will not restart, even if you provide a start condition after the initial end condition!
For example:
Let's assume that your SLA will start when the status is To Do and end when the status is Done. Once you move the issue to To Do, your SLA will start counting until providing the end condition on this issue. When your status is Done, your SLA will never start again.
⭐ Even if you move the issue from Done to To Do, your SLA will not start, and Time to SLA will not take other cycles into account.
If you select this method, your SLA will only calculate the first cycle, which means you’ll never be able to restart the SLA afterward.
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.
After meeting the end condition, if you provide the start condition again, Time to SLA will invalidate the previous cycle and your SLA will start again.
For example:
Let's assume that your SLA will start when the status is To Do and end when the status is Done. Once you move the issue to To Do, your SLA will count until it provides the end condition on this issue.
⭐ When you move the issue Done to To Do, your SLA will reset the elapsed duration and start from the beginning.
Moreover, this method displays the value of your SLA since the last Start condition was met. You can restart the SLA, but it will always display only the most recent cycle.
You can choose this method to keep the last comment’s time in the panel. This will tell you when the last comment was submitted and whether it aligned with your target 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.
After meeting the end condition, if you provide the start condition again, your SLA will resume without resetting the elapsed duration.
For example:
Let's assume that your SLA will start when the status is To Do and end when the status is Done. Once you move the issue to To Do, your SLA will count until it provides the end condition on this issue.
⭐ When you change the status of the issue from Done to To Do, your SLA will resume on the previous elapsed duration. Please keep in mind that the elapsed duration will not continue to count between the end and start conditions.
This means that no matter how many statuses you change, your SLA will always pick up where it left off. It’s quite literally the sum of all cycles!
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.
After meeting the end condition, if you provide the start condition again, your SLA will resume without resetting the elapsed duration.
For example:
Let's assume that your SLA will start when the status is To Do and end when the status is Done. Once you move the issue to To Do, your SLA will count until it provides the end condition on this issue.
⭐ When you change the status of the issue from Done to To Do, your SLA will resume on the previous elapsed duration. Please keep in mind that, that unlike the All Cycles method, the Largest Span also takes into account intermediary statuses.
In a nutshell, this method takes into account all processes from the start of the SLA to the time it is resolved.
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:
