---
title: "How to trigger Automation for Jira based on SLA breaches"
canonical: "https://support.appfire.com/space/TTS/49742237/How%20to%20trigger%20Automation%20for%20Jira%20based%20on%20SLA%20breaches"
format: markdown
---
> Macro (aura-html)

With Time to SLA, you can trigger Jira automation rules based on SLA breaches. Follow the steps below to configure an automation rule.

## Prerequisites

Before you begin, ensure that:

- You have **Time to SLA** installed and configured in your Jira instance.
- You have **Automation for Jira** installed and are using the **paid version** (third-party integrations are not available in the Lite version).
- You have the necessary **Jira administrator or project administrator permissions** to create automation rules.

## Steps

1. <span style="color: #000000">Go to the </span><span style="color: #000000">**Automation Rules**</span><span style="color: #000000"> page.</span>
2. <span style="color: #000000">Click </span><span style="color: #000000">**Create Rule.**</span>
3. <span style="color: #000000">Click </span><span style="color: #000000">**SLA threshold breached (Time to SLA)**</span><span style="color: #000000">.</span>
4. <span style="color: #000000">Select </span><span style="color: #000000">**SLAs, Trigger type, Repeat interval(optional), Enable working calendar(optional)**</span><span style="color: #000000">.</span>
  - **SLAs - **Add notifiers to the selected SLAs.
  - **Trigger when SLA – **Your options are:
    - **Is breached:** When the SLA is breached, the rule will be triggered.
    - **Will be breached in:** Define a duration and rule will be triggered when there is time left as much as specified duration to SLA breach.
    - **Has been breached for:** Define a duration and rule will be triggered after the SLA breach and that duration pass.
    - **Has reached:** When the specified percentage of SLA reached, the rule will be triggered.
  - **Repeat every –** When enabled, the trigger will be repeated at every given interval.
  - **Enable working calendar – **When enabled, the trigger will be based on working calendars.
    For example, in a 9 AM-5 PM and Monday-Friday calendar, a trigger set for 1d before an SLA is breached at 12 PM on Monday will be triggered at 12 PM on the previous Friday.
5. <span style="color: #000000">Click</span><span style="color: #000000">** Save.**</span>

## Smart values

| **Parameter** | **Type** | **Description** |
| --- | --- | --- |
| `slaName` | String | Name of the SLA |
| `slaDuration` | String | <span style="color: #172b4d">SLA value as a time string</span> |
| `remainingDuration` | String | Remaining time of the SLA as a time string |
| `breachDuration` | String | Breach time of the SLA as a time string |
| `elapsedDuration` | String | Elapsed time of the SLA as a time string |
| `pausedDuration` | String | Paused time of the SLA as a time string |
| `startDate` | Date | <span style="color: #172b4d">Start time of the SLA</span> |
| `endDate` | Date | <span style="color: #172b4d">End time of the SLA</span> |
| `targetDate` | Date | <span style="color: #172b4d">Deadline of the SLA</span> |