In order to achieve the full potential of the SLA Timer Add-on a few Add-on concepts must be explained.
SLA
The SLA is the core object of the add-on.
A SLA is paired with a JIRA search (saved filter or jql) for issues and a Schedule (se below).
The SLA will define the allowed time for issues in scope of a SLA. Likewise an optional First Response time.
Schedule
A Schedule defines working hours monday to sunday.
A SLA is paired with a Schedule and an issue within scope of a SLA will only increase in SLA Spent Time with the Schedule
...
defined working hours.
A Schedule can be configured to use holidays. If it is a holiday an an issue within scope of a SLA will not increase in SLA Spent Time.
Overdue - Issue
...
Overdue
An issue is considered overdue if the SLA Percent is greather than or equals to equal to 100 %.
On Time - Issue On Time
An issue is considered on time if the SLA Percent is less than 100 %.
SLA Target Time
The Target Time or the SLA Target Time is the maximum time which can be spent on a issue.
The SLA Target Time is configured at Add-on configuration pages. A SLA Target Time can be configured for each SLA.
SLA Time Spent
Time Spent is the amount of time an issue has been in scope of a SLA. Spent Time is only increasing when also with within the Schedule configured paired with a SLA.
SLA Status
The SLA Status is determined automatically by the Add-on. It describes the state of an issue in terms of the actually spent time versus the SLA Target Time.
...