---
title: "Detailed feature comparison"
canonical: "https://support.appfire.com/space/TTS/2811658241/Detailed%20feature%20comparison"
format: markdown
---
> Macro (aura-html)

> ℹ️ The information on this page was last updated on 4/17/2026.

# Intro

The main parameters to consider for comparison are listed below.

The comparison table reflects the customer's view based on menu items. See the parity tables of Time to SLA features below for details.

# Main features

## SLAs

This is the home page for SLA admins to perform essential tasks, such as listing, creating, updating, and deleting SLA configurations.  

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| **List / Filter SLAs** |  | :check_mark: | :check_mark: | The SLAs page lists and filters existing SLA configurations, though it has no specific label or menu section in the UI. |
| Columns | :check_mark: | :check_mark: |  |
| Hide disabled SLAs | :check_mark: | :check_mark: |  |
| View SLA | :check_mark: | :check_mark: |  |
| Edit SLA | :check_mark: | :check_mark: | In Cloud, this appears in the overflow menu as three dots. |
| Notifications | :check_mark: | :check_mark: | In Cloud, this appears in the overflow menu as three dots. |
| Duplicate SLA | :check_mark: | :check_mark: | In Cloud, this appears in the overflow menu as three dots. |
| Delete SLA | :check_mark: | :check_mark: | In Cloud, this appears in the overflow menu as three dots. |
| **Import JSM SLAs** | :check_mark: | :cross_mark: |  |
| **Add New SLA Definition** | :check_mark: | :check_mark: | We overhauled the entire UX/UI after a year to make Time to SLA user-friendly for existing customers, trial users, and novice SLA admins. |
| Create from **template** | :cross_mark: | :check_mark: | [Time to SLA Cloud offer templates](https://appfire.atlassian.net/wiki/x/WYA6Ag) for the most commonly used scenarios: Time to resolution, Time to first response, and Time in "In Progress". |
| Create from **scratch** | :check_mark: | :check_mark: |  |
| SLA Name |  | :check_mark: | :check_mark: |  |
| Enable SLA |  | :check_mark: | :check_mark: | You can access it from the three dots menu on the SLA home page when selecting an existing SLA. |
| SLA Scope |  | :check_mark: | :check_mark: |  |
| Projects | :check_mark: | :check_mark: |  |
| Issues (JQL) | :check_mark: | :cross_mark: | Although JQL is unavailable in the SLA scope, you can use it in the SLA Goal definition. Users can still use JQL whenever needed. |
| Workflow | :check_mark: | :cross_mark: | This legacy feature has been removed.<br>You can achieve the same outcome by adding corresponding projects or work item types in the SLA definition. |
| Conditions |  | :check_mark: | :check_mark: |  |
| Grouped Conditions | :cross_mark: | :check_mark: | Grouped conditions are used to enforce [All / Any of the following conditions](https://appfire.atlassian.net/wiki/spaces/TTSC/pages/35456221/SLA+conditions#Grouped-conditions). |
| Start |  | :check_mark: | :check_mark: |  |
| Status is changed | :check_mark: | :check_mark: |  |
| Field value is changed | :check_mark: | :check_mark: |  |
| Comment is made | :check_mark: | :check_mark: |  |
| Date field is reached | :check_mark: | :check_mark: | Renamed as `Date field is met`. |
| Triggered by another SLA | :cross_mark: | :check_mark: |  |
| End |  | :check_mark: | :check_mark: |  |
| Status is changed | :check_mark: | :check_mark: |  |
| Field value is changed | :check_mark: | :check_mark: |  |
| Comment is made | :check_mark: | :check_mark: |  |
| Date field is reached | :check_mark: | :check_mark: | Renamed as `Date field is met`. |
| Triggered by another SLA | :cross_mark: | :check_mark: |  |
| Reset |  | :check_mark: | :check_mark: |  |
| Status is changed | :check_mark: | :check_mark: |  |
| Field value is changed | :check_mark: | :check_mark: |  |
| Comment is made | :check_mark: | :check_mark: |  |
| Date field is reached | :check_mark: | :check_mark: | Renamed as `Date field is met`. |
| Pause |  | :check_mark: | :check_mark: |  |
| Status is any of selected status(es)... | :check_mark: | :check_mark: |  |
| Field value satisfies a condition... | :check_mark: | :check_mark: | ⚠️ These clauses are not available on Cloud: Is not equal to any of the selected values and is not empty... |
| Triggered by another SLA | :cross_mark: | :check_mark: |  |
| Goals |  | :check_mark: | :check_mark: |  |
| (Enable) All remaining issues | :check_mark: | :check_mark: |  |
| Add new SLA goal |  | :check_mark: | :check_mark: |  |
| Issues (JQL) | :check_mark: | :check_mark: |  |
| Priority | :check_mark: | :check_mark: |  |
| Issue Type | :cross_mark: | :check_mark: |  |
| Request Type | :cross_mark: | :check_mark: |  |
| Assignee | :cross_mark: | :check_mark: |  |
| Issue Filter | :cross_mark: | :check_mark: |  |
| Goal (type) |  | :check_mark: | :check_mark: |  |
| Negotiation Date | :check_mark: | :check_mark: |  |
| Dynamic Duration | :check_mark: | :check_mark: | On Cloud, [the same capability](https://appfire.atlassian.net/wiki/x/tIAiAg) exists with one difference: Cloud lacks a built-in duration custom field, so users select text-based custom fields to define dynamic duration goals. |
| Duration | :check_mark: | :check_mark: |  |
| Next Business Day | :check_mark: | :check_mark: |  |
| No Target | :check_mark: | :check_mark: |  |
| Goal (value) | :check_mark: | :check_mark: |  |
| Calendar |  | :check_mark: | :check_mark: |  |
| Add New Calendar | :cross_mark: | :check_mark: |  |
| Select Calendar via Jira Issue | :cross_mark: | :check_mark: |  |
| Choose existing calendars | :check_mark: | :check_mark: |  |
| Order | :check_mark: | :check_mark: | Users can rank their goals using chevrons, but there is no explicit label or menu. |
| Calculation Method | :check_mark: | :check_mark: |  |
| Critical Zone | :check_mark: | :check_mark: |  |
| Event Order | :cross_mark: | :check_mark: |  |
| Linked Issue SLA |  | :cross_mark: | :check_mark: |  |
| The "Push" Action | Share this SLA on linked issues | :cross_mark: | :check_mark: | This option makes <u>this issue’s</u> SLA panel visible on linked issues. This is ideal for creating shared accountability, like making a 'Dev' team aware of the main 'Customer' SLA. |
| The "Pull" Action | Display linked issues' SLAs | :cross_mark: | :check_mark: | This option displays all SLAs from linked issues *on this issue*. This is ideal for tracking dependencies, like monitoring all sub-tasks for an "Employee Onboarding" ticket. |
| Asynchronous Update | :check_mark: | :cross_mark: | On Cloud, every update must be asynchronous by design, so no explicit configuration option is needed for this feature. |
| **Notifiers** | :check_mark: | :check_mark: |  |
| List Notifiers |  | :check_mark: | :check_mark: |  |
| Edit | :check_mark: | :check_mark: |  |
| Delete | :check_mark: | :check_mark: |  |
| Associate with goals | :check_mark: | :check_mark: |  |
| Add New SLA Notification |  | :check_mark: | :check_mark: |  |
| Enable Notifier | :check_mark: | :check_mark: |  |
| Trigger When SLA | :check_mark: | :check_mark: |  |
|  | is breached | :check_mark: | :check_mark: |  |
|  | will be breached in | :check_mark: | :check_mark: |  |
|  | has been breached for | :check_mark: | :check_mark: |  |
|  | has reached (% of SLA Goal) | :check_mark: | :check_mark: | Renamed as `has reached`. |
|  | is over | :check_mark: | :check_mark: |  |
| Repeat every | :check_mark: | :check_mark: |  |
| Enable working calendar | :check_mark: | :check_mark: |  |
| When triggered |  | :check_mark: | :check_mark: |  |
| Send an email |  | :check_mark: | :check_mark: |  |
| Default recipients |  | :check_mark: | :check_mark: |  |
| Assignee | :check_mark: | :check_mark: |  |
| Reporter | :check_mark: | :check_mark: |  |
| Project lead | :check_mark: | :cross_mark: |  |
| Component lead(s) | :check_mark: | :cross_mark: |  |
| Voters | :check_mark: | :check_mark: |  |
| Watchers | :check_mark: | :check_mark: |  |
| Custom recipients |  | :check_mark: | :check_mark: |  |
| Jira Users | :check_mark: | :check_mark: |  |
| Group | :check_mark: | :check_mark: |  |
| User Field | :check_mark: | :check_mark: |  |
| Group Field | :check_mark: | :check_mark: |  |
| Project Role | :check_mark: | :cross_mark: |  |
| Email Address | :check_mark: | :cross_mark: |  |
| Other Recipient Types |  | :check_mark: | :cross_mark: |  |
| CC | :check_mark: | :cross_mark: |  |
| BCC | :check_mark: | :cross_mark: |  |
| Preview Email Content | :check_mark: | :cross_mark: |  |
| Send a Slack message | :check_mark: | :check_mark: |  |
| Fire an event | :check_mark: | :check_mark: |  |
| Trigger a Jira Automation Rule | :cross_mark: | :check_mark: |  |

## Calendars

This is the main function to allows users to set their business working hours. The working hours set in the calendar are used to calculate SLA durations. 

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| **List/Filter Calendars** |  | :check_mark: | :check_mark: |  |
| View | :check_mark: | :check_mark: |  |
| Edit | :check_mark: | :check_mark: |  |
| Delete | :check_mark: | :check_mark: |  |
| **Add New Calendar** |  | :check_mark: | :check_mark: | The calendar experience in Cloud has been redesigned to simplify configuring business hours, breaks, and holidays. |
| Name | :check_mark: | :check_mark: |  |
| Region | :check_mark: | :check_mark: | In Cloud, Region and Time Zone form a single UI component rather than two. |
| Time Zone | :check_mark: | :check_mark: |  |
| **Business Hours** |  | :check_mark: | :check_mark: |  |
| Working Day | :check_mark: | :check_mark: |  |
| Working Hours | :check_mark: | :check_mark: | Unlike the 24-hour shifts in DC, a maximum shift on Cloud runs from 00:00 to 23:59. |
| Length of Business Day |  | :check_mark: | :check_mark: | In Cloud, it has been moved to the **Advanced** section. |
| **Holidays** | :check_mark: | :check_mark: |  |
| Show Past | :check_mark: | :check_mark: | Cloud has a single `Show previous holidays` option instead of separate buttons for showing and hiding past holidays. |
| Hide Past | :check_mark: | :check_mark: |  |
| Add Holiday (+) |  | :check_mark: | :check_mark: |  |
| Name | :check_mark: | :check_mark: |  |
| Date | :check_mark: | :check_mark: |  |
| Recurring | :check_mark: | :check_mark: |  |
| Type | :check_mark: | :check_mark: |  |
| **Shared Holidays** | :check_mark: | :check_mark: |  |
| Show Past | :check_mark: | :check_mark: |  |
| Hide Past | :check_mark: | :check_mark: |  |
| Add Shared Holiday (+) |  | :check_mark: | :check_mark: |  |
| Name | :check_mark: | :check_mark: |  |
| Date | :check_mark: | :check_mark: |  |
| Recurring | :check_mark: | :check_mark: |  |
| Type | :check_mark: | :check_mark: |  |

## SLA fields

These are SLA-related custom fields to enrich the Jira work item view.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| TTS - Time to SLA | :check_mark: | :cross_mark: | *This field (Time to SLA field on DC) is supported as the “[TTS - SLA Duration](https://appfire.atlassian.net/wiki/spaces/TTSC/pages/2969239557)” on Cloud, with only a few configuration differences.<br>Cloud users can also utilize the [Linked Issue SLA](https://appfire.atlassian.net/wiki/x/awAgAg) feature as a workaround if they currently use this custom field to configure Display SLAs of linked issues on DC. |
| TTS - Overdue Status | :check_mark: | :cross_mark: |  |
| TTS - SLA Indicator | :check_mark: | :check_mark:* | *As the field functionality differs, we recommend you check the [documentation](https://appfire.atlassian.net/wiki/spaces/TTSC/pages/2878930952). |
| TTS - SLA Overview | :check_mark: | :cross_mark: |  |
| TTS - Duration Field | :check_mark: | :check_mark:* | *Users can define an SLA goal with a [dynamic duration using a text-only custom field.](https://appfire.atlassian.net/wiki/x/tIAiAg) |
| TTS - SLA Date | :check_mark: | :check_mark:* | *As the field functionality differs, we recommend you check the [documentation](https://appfire.atlassian.net/wiki/spaces/TTSC/pages/2879160326). |

## SLA panels

Color-coded panel for Jira work item view. s

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Auto refresh | :check_mark: | :check_mark: | The SLA Panel in the issue view refreshes automatically when significant events occur. For example, when the current user moves the issue to done status, the SLA Panel updates its status and color codes without needing to refresh the Jira work item. |
| Show in SLA panel | :check_mark: | :check_mark: | The SLA Panel appears under the “Settings” menu in Cloud, not as a separate item. |
| Duration Format | :check_mark: | :check_mark: |  |
| SLA Context | :check_mark: | :check_mark: |  |
| External issue changes | :check_mark: | :check_mark: |  |
| Hide Completed SLAs | :check_mark: | :check_mark: |  |
| Out of working hours | :check_mark: | :check_mark: |  |
| Not started SLAs | :check_mark: | :check_mark: |  |
| Panel Position (Display Options) | :check_mark: | :check_mark: | The Panel Position (Top/Bottom) option is unavailable on Cloud due to Atlassian’s framework limitations, so the SLA panel cannot be placed at the top in the issue view. |
| SLA Order | :check_mark: | :check_mark: |  |
| Hide Paused SLAs | :cross_mark: | :check_mark: |  |

## Permissions

This is the main place to grant the SLA admin role to Jira users and to assign permissions granularly.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Define TTS Admins |  | :check_mark: | :cross_mark: | - **Permissions** tab is represented in the **Settings** menu in Cloud rather than a separate menu item.
- Although there is no explicit `TTS Admins` definition on Cloud, there is no functionality loss because users still grant permissions in the same manner. For example, assigning Calendars to certain groups or users. |
| Jira Admins | :check_mark: | :cross_mark: |  |
| Groups | :check_mark: | :cross_mark: |  |
| Users | :check_mark: | :cross_mark: |  |
| Granular permission for each view, create, update, and delete operation | :check_mark: | :cross_mark: |  |
| Calendar Configuration | :check_mark: | :check_mark: |  |
| SLA Configuration | :check_mark: | :check_mark: |  |
| Notifier Configuration | :check_mark: | :cross_mark: | Cloud has no explicit permission for notifiers because notifications fall under SLA configurations. The `SLA Configuration` permission covers both. |
| SLA Fields/Panels | :check_mark: | :check_mark: |  |
| SLA Panel Customization | :check_mark: | :check_mark: |  |
| Custom Fields Configuration | :check_mark: | :cross_mark: | This is because no custom fields are available on Cloud yet. |
| SLA Recalculation | :check_mark: | :check_mark: |  |
| Report | :check_mark: | :check_mark: |  |
| Import/Export | :check_mark: | :check_mark: |  |
| Issue View Menu SLA Actions | :check_mark: | :check_mark: |  |

## SLA report

This is main place to create reports and subscriptions for periodic delivery.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| **Export** |  | :check_mark: | :check_mark: |  |
| **Search** |  | :check_mark: | :check_mark: |  |
| Save filter as | :check_mark: | :check_mark: |  |
| Format | :check_mark: | :check_mark: |  |
| Issue Columns | :check_mark: | :check_mark: |  |
| Report Type |  | :check_mark: | :check_mark: |  |
| SLA Summary | :check_mark: | :check_mark: |  |
| SLA Detail | :check_mark: | :check_mark: |  |
| SLA Durations | :check_mark: | :check_mark: |  |
| SLA Status | :check_mark: | :check_mark: |  |
| Filter Type |  | :check_mark: | :check_mark: |  |
| Project | :check_mark: | :check_mark: |  |
| JQL | :check_mark: | :check_mark: |  |
| Issue Filters | :check_mark: | :check_mark: |  |
| SLAs | :check_mark: | :check_mark: |  |
| More |  | :check_mark: | :check_mark: |  |
| SLA Start Date | :check_mark: | :check_mark: |  |
| SLA Target Date | :check_mark: | :check_mark: |  |
| SLA End Date | :check_mark: | :check_mark: |  |
| SLA State | :check_mark: | :check_mark: |  |
| SLA Indicator | :check_mark: | :check_mark: |  |
| Remaining | :check_mark: | :check_mark: |  |
| Elapsed | :check_mark: | :check_mark: |  |
| Critical Zone | :check_mark: | :check_mark: |  |
| Is SLA Extended | :cross_mark: | :check_mark: |  |
| Clear filters | :check_mark: | :check_mark: |  |
| **Generate** |  | :check_mark: | :check_mark: |  |
| Execute | :check_mark: | :check_mark: | This is the typical user behaviour when pressing the **Generate** button. |
| Schedule | :check_mark: | :check_mark: | Users can find this option in the menu accessed by clicking the chevron next to the **Generate** button. |
| Background | :check_mark: | :check_mark: | This appears in the menu when users click the chevron next to the **Generate** button. |

## SLA recalculation

This is for recalculating the SLA data when users need to refresh SLA metrics.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| JQL | :check_mark: | :check_mark: | On Cloud, each [recalculation](https://appfire.atlassian.net/wiki/x/oAUdAg) task handles up to 20,000 work items and 10 SLA configurations. |
| SLAs | :check_mark: | :check_mark: |  |
| Recalculation Concurrency | :check_mark: | :cross_mark: | This is unavailable on Cloud because it lacks threading capabilities. By design, every operation works in a threaded way. |
| Exclude Finished SLAs | :check_mark: | :check_mark: |  |

## Integrity checker

This is for scanning the database for out-of-date SLA related information similar to the Jira one for admins.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Integrity Checker | :check_mark: | :cross_mark: |  |
| SLA configuration | :check_mark: | :cross_mark: |  |
| Issue SLA data | :check_mark: | :cross_mark: |  |
| Redundant configuration | :check_mark: | :cross_mark: |  |
| Scheduled Tasks | :check_mark: | :cross_mark: |  |
| SLA function configuration | :check_mark: | :cross_mark: |  |

## Settings

This is where users can change the settings of the Time to SLA app.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| General |  | :check_mark: | :check_mark: | In Cloud, the only setting in **General** is the timezone for the 24/7 calendar. |
| Time Format (Long/Short/Shorter) | :check_mark: | :cross_mark: |  |
| Overview Tab JQL | :check_mark: | :cross_mark: |  |
| SLA Panel JQL | :check_mark: | :cross_mark: |  |
| TTS Menu JQL | :check_mark: | :cross_mark: |  |
| SLA Status Labels |  | :check_mark: | :cross_mark: |  |
| Localizable Indicator | :check_mark: | :cross_mark: |  |
| Use i18n keys | :check_mark: | :cross_mark: |  |
| Met | :check_mark: | :cross_mark: |  |
| Progress | :check_mark: | :cross_mark: |  |
| Exceeded | :check_mark: | :cross_mark: |  |
| Inactive | :check_mark: | :cross_mark: |  |
| Paused | :check_mark: | :cross_mark: |  |
| Invalid | :check_mark: | :cross_mark: |  |
| SLA Notifiers | :check_mark: | :check_mark: | Renamed as `SLA Notification Template`. |
| SLA Calculation Scope | :check_mark: | :check_mark: |  |
| Scheduled Tasks | :check_mark: | :cross_mark: | No functionality is lost because it applies intrinsically to the backend SLA services. |
| Escalation Services | :check_mark: | :cross_mark: | - The name can be misleading because the functionality schedules SLA recalculation.
- Given the cost of Cloud operations, we recalculate only on demand, not on a schedule. |
| Cache | :check_mark: | :cross_mark: | It does not apply on Cloud. |
| Advanced Configuration |  | :check_mark: | :check_mark: |  |
| Report Scope Limit | :check_mark: | :cross_mark: | Cloud has an internal limitation. |
| JQL Rows Limit | :check_mark: | :cross_mark: | Cloud has an internal limitation. |
| Gadget Issue Limit | :check_mark: | :cross_mark: | Cloud has an internal limitation. |
| Recurring Notifier Limit | :check_mark: | :cross_mark: | Cloud has an internal limitation. |
| Recalculation Concurrency | :check_mark: | :cross_mark: | Not technically feasible on Cloud. |
| Asynchronous Calculation Thread Type | :check_mark: | :cross_mark: | Not technically feasible on Cloud. |
| Asynchronous Calculation Thread Count | :check_mark: | :cross_mark: | Not technically feasible on Cloud. |
| System-wide asynchronous SLA calculations | :check_mark: | :cross_mark: | Not technically feasible on Cloud. |
| Support Tools | :check_mark: | :cross_mark: | Not technically feasible on Cloud. |

## Import/Export

This is the traditional backup restore function for the existing instance.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Export | :check_mark: | :check_mark: |  |
| Import | :check_mark: | :check_mark: |  |
| Import JSM SLAs | :check_mark: | :cross_mark: |  |

## License management

This is a legacy feature and not applicable on Cloud.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| License Information: Time to SLA (TTS) |  | :check_mark: | :cross_mark: |  |
| License information issued by Atlassian Marketplace | :check_mark: | :cross_mark: |  |
| License information issued by Appfire | :check_mark: | :cross_mark: |  |

## Time to SLA preferences

**Brief Description:**

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Time to SLA preferences |  | :check_mark: | :cross_mark: | This is a legacy design choice and should be under settings. |
| Preferences | :check_mark: | :cross_mark: | Not feasible in the cloud |
| Mute SLA Notifications | :check_mark: | :check_mark: | It is available via Atlassian User Profile |

# Features in project settings

## Customer Portal SLAs 

This is the place to add existing SLAs to customer portal.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Customer Portal SLAs | :check_mark: | :check_mark: | According to Atlassian’s new design language, projects are called “spaces”. This feature is available under Service space > **Settings** > **Apps** > **Time to SLA**. |
| Define For All Request Types | :check_mark: | :check_mark: |  |
| Selected Request Type | All SLAs | :check_mark: | :check_mark: |  |
| Some SLAs | :check_mark: | :check_mark: |  |
| No SLA | :check_mark: | :check_mark: |  |

# Features in workflow

## Conditions

Conditions are used to check to make sure the user should be able to perform a transition.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Conditions | :cross_mark: | :cross_mark: | No conditions available on both hosting types. |

## Validators

Validators are rules that check for specific criteria to be met after a user attempts a transition, preventing the issue from moving to a new status if the validation fails.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Validators | :cross_mark: | :cross_mark: | No validators available on both hosting types. |

## Post functions

Post functions are used to execute automated actions after the transition is performed.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| TTS - Release Re-index Queue of the Issue | :check_mark: | :cross_mark: | Technically not feasible on Cloud. |
| TTS - Reset SLA | :check_mark: | :check_mark: |  |

# Features in dashboards

## Gadgets 

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| SLA Status Pie Chart | :check_mark: | :cross_mark: |  |
| TTS - Periodic Met vs Exceeded Issue | :check_mark: | :cross_mark: |  |
| TTS - Periodic Met vs Exceeded SLA | :check_mark: | :check_mark: |  |
| TTS - SLA Durations | :check_mark: | :cross_mark: |  |
| TTS - SLA Success/Fail Counts Chart | :check_mark: | :cross_mark: |  |
| TTS - SLA Success/Fail Rates Chart | :check_mark: | :cross_mark: |  |
| TTS - SLA Working Duration Analysis | :check_mark: | :cross_mark: |  |
| TTS - SLA/Assignee Performance Gadget | :cross_mark: | :check_mark: |  |

# Features in issue search

## JQL functions

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| State functions |  | :check_mark: | :cross_mark: |  |
| - isNotStarted([Optional List of SLA IDs or/and Name(s)])
- isFinished([Optional List of SLA IDs or/and Name(s) ])
- isRunning([Optional List of SLA IDs or/and Name(s)])
- isPaused([Optional List of SLA IDs or/and Name(s)]) | :check_mark: | :cross_mark: |  |
| Duration functions |  | :check_mark: | :cross_mark: |  |
| - remainingDuration(Duration, [Optional List of SLA IDs or/and Name(s)])
- elapsedDuration(Duration, [Optional List of SLA IDs or/and Name(s)])
- breachDuration(Duration, [Optional List of SLA IDs or/and Name(s)]) | :check_mark: | :cross_mark: |  |
| Date functions |  | :check_mark: | :cross_mark: |  |
| - slaStartDate(Date or Duration or timeFunction, [Optional List of SLA IDs or/and Name(s)])
- slaTargetDate(Date or Duration or timeFunction, [Optional List of SLA IDs or/and Name(s)])
- slaEndDate(Date or Duration or timeFunction, [Optional List of SLA IDs or/and Name(s)]) | :check_mark: | :cross_mark: |  |
| Percentage functions |  | :check_mark: | :cross_mark: |  |
| - remainingPercentage(Percentage, [Optional List of SLA IDs or/and Name(s)])
- elapsedPercentage(Percent, [Optional List of SLA IDs or/and Name(s)]) | :check_mark: | :cross_mark: |  |
| Breach functions |  | :check_mark: | :cross_mark: |  |
| isBreached([Optional List of SLA IDs or/and Name(s)]) | :check_mark: | :cross_mark: |  |
| Critical zone functions |  | :check_mark: | :cross_mark: |  |
| isInCriticalZone([Optional List of SLA IDs or/and Name(s)]) | :check_mark: | :cross_mark: |  |
| Business hours functions |  | :check_mark: | :cross_mark: |  |
| isInBusinessHours([Optional List of SLA IDs or/and Name(s)]) | :check_mark: | :cross_mark: |  |
| Contains SLA function |  | :check_mark: | :cross_mark: |  |
| containsSla([List of at least 1 SLA ID or/and Name(s)]) | :check_mark: | :cross_mark: |  |
| Complex functions |  | :check_mark: | :cross_mark: |  |
| - isMet([Optional List of SLA IDs or/and Name(s)])
- isAllMet([Optional List of SLA IDs or/and Name(s)])
- isNotBreachedAndNotFinished([Optional List of SLA IDs or/and Name(s)])
- isAllNotBreachedAndNotFinished([Optional List of SLA IDs or/and Name(s)]) | :check_mark: | :cross_mark: |  |
| SLA definition queries |  | :check_mark: | :cross_mark: |  |
| - slaFunction is EMPTY
- slaFunction is not EMPTY | :check_mark: | :cross_mark: |  |

# **Features in work item view**

## Work item actions

These are work item-specific SLA actions that can be accessed via Jira work item view.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| **Issue Actions** |  | :check_mark: | :check_mark: |  |
| SLA Report | :check_mark: | :cross_mark: |  |
| Reset SLA | :check_mark: | :check_mark: |  |
| Undo Reset SLA | :check_mark: | :check_mark: |  |
| Where is My SLA? | :check_mark: | :check_mark: |  |
| Regenerate SLA Data | :check_mark: | :check_mark: |  |
| Mute SLA | :check_mark: | :check_mark: |  |
| **SLA History** | :check_mark: | :check_mark: |  |
| **SLA Overview** | :check_mark: | :cross_mark: |  |
| **SLA Panel** |  | :check_mark: | :check_mark: |  |
| SLA Info :info: | :check_mark: | :check_mark: | This is a shortcut menu to open SLA configuration details. |
| SLA Contract Extension | :cross_mark: | :check_mark: | [This is a new feature](https://appfire.atlassian.net/wiki/x/LwNMdw) to handle exceptional cases and extend SLAs per issue. |


# Features in non-GUI access

## REST APIs

This allows programmatic access to SLA data.

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Calendars | :check_mark: | :check_mark: |  |
| SLA Configurations | :check_mark: | :check_mark: |  |
| Custom Fields | :check_mark: | :check_mark: |  |
| Issue SLAs | :check_mark: | :check_mark: |  |
| Recalculation | :check_mark: | :check_mark: |  |
| Reports | :check_mark: | :check_mark: |  |
| Permissions | :check_mark: | :check_mark: |  |
| Notifiers | :check_mark: | :check_mark: |  |

# Integrations

## App integrations

This is for a better-together experience by integrating other apps. 

| **Feature/Parameter** | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- |
| Better Excel Exporter | :check_mark: | :cross_mark: |  |
| Configuration Manager for Jira | :check_mark: | :cross_mark: |  |
| eazyBI | :check_mark: | :check_mark: |  |
| Theme Extension for JSM | :check_mark: | :cross_mark: |  |
| PowerBI Connector for Jira | :check_mark: | :cross_mark: |  |
| Automation for Jira | :check_mark: | :check_mark: | On Cloud, you can [trigger Jira automation rules via notifiers](https://appfire.atlassian.net/wiki/x/kgVEVw). |
| Dashboard Hub Pro (Charts, Reports, Time in Status for Jira) | :cross_mark: | :check_mark: |  |