---
title: "Time to SLA feature differences between Jira Data Center and Cloud"
canonical: "https://support.appfire.com/space/TTS/46432949/Time%20to%20SLA%20feature%20differences%20between%20Jira%20Data%20Center%20and%20Cloud"
format: markdown
---
> Macro (aura-html)

> ℹ️ Last updated: 4/17/2026

> ✅ This page provides a high-level overview of Data Center and Cloud feature differences. If you’d like a more detailed breakdown, refer to the in-depth [feature comparison page](https://appfire.atlassian.net/wiki/spaces/TTSC/pages/2760802311).

## Advantages of Time to SLA for Jira Cloud

The Cloud version of Time to SLA is designed to minimize administrative work, support complex business processes, and provide a guided, ready-to-use setup for teams of any size.

<details>
<summary>Click to learn more about the benefits:</summary>

Each improvement in the cloud contributes to one of three main areas: a smarter administrator experience, advanced process control, and global collaboration. Here’s what you and your teams will gain:

### **A smarter, faster administrator experience**

We've redesigned the administrator experience to significantly reduce the learning curve and the time spent on configuration.

- **Get started in minutes:** A new **Onboarding Helper** provides a getting-started guide and ready-made solutions for common goals (like tracking compliance or improving response times).
- **Build SLAs with confidence:** Create new SLAs in four easy, well-defined steps, or use templates to get started even faster.
- **Eliminate JQL guesswork:** Our goal definition tool features built-in filters for issue type, request type, and assignee, making it user-friendly for novice administrators and reducing the need for complex JQL.
- **Automated best practices:** We automatically create built-in notifiers (like 50% elapsed time reminders) for every new SLA, saving you setup time and ensuring your teams are always proactive.

### **Powerful, real-world process control**

Cloud enables sophisticated, enterprise-grade logic that mirrors your true business processes, no matter how complex.

- **Chain SLAs together:** You can now trigger SLAs based on other SLAs. This lets you build true "chain of command" workflows (for example, when the *UX SLA* completes, the *Dev SLA* automatically starts, which then triggers the *QA SLA*).
- **Handle any contractual need:** Easily create grouped (All/Any) conditions to build sophisticated rules that match your most complex enterprise contracts.
- **Flexible, real-world adjustments:** Admins can grant issue-level contract extensions for one-off customer-approved delays, ensuring reports are accurate and teams aren't penalized for exceptions.
- **Manage event "race conditions":** A new setting lets you override the default event order (start/pause/stop), giving you precise control when two events happen at the exact same moment.

### **Unmatched multi-team and global operations**

The cloud version is built for how modern, distributed teams work. It breaks down silos between departments and time zones.

- **Dynamic calendars:** You can now use dynamic calendar selection based on an issue field. This is a massive win for global teams, empowering users in different time zones to customize SLAs on the fly without forcing admins to create dozens of separate goals.
- **Create shared accountability (The "push"):** You can "push" a primary SLA's panel onto linked issues. This makes a customer-facing SLA visible to internal teams (like DevOps), ensuring everyone understands the urgency.
- **Build a "mission control" (The "pull"):** You can "pull" all SLA panels from linked issues and display them on a master ticket. This is perfect for managing complex processes (like employee onboarding) from a single "mission control" view.
</details>

For details on how the data center and cloud versions compare, refer to the table below.

| **Feature/Parameter** |  | **DC** | **Cloud** | **Notes** |
| --- | --- | --- | --- | --- |
| Main features |  | :check_mark: | :check_mark: |  |
| Onboarding helper (Getting Started Guide) | :cross_mark: | :check_mark: |  |
| List / Filter SLAs | :check_mark: | :check_mark: |  |
| Import JSM SLAs | :check_mark: | :cross_mark: |  |
| Add new SLA definition from template | :cross_mark: | :check_mark: |  |
| Create new SLA definition from scratch | :check_mark: | :check_mark: |  |
| Define SLA Scope | :check_mark: | :check_mark: |  |
| Condition Definitions (Start/Stop/Pause/Reset) | :check_mark: | :check_mark: |  |
| Condition Based on other SLAs | :cross_mark: | :check_mark: |  |
| Conditions with pre-filled common settings | :cross_mark: | :check_mark: | Such as a start condition, such as `Issue is Created`, or a stop condition, such as `Issue Resolved`. |
| Grouped conditions | :cross_mark: | :check_mark: |  |
| Goal definition | :check_mark: | :check_mark: |  |
| Goals definition with built-in issue type, request type, assignee and issue filter. | :cross_mark: | :check_mark: |  |
| 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: |  |
| Notifiers definition | :check_mark: | :check_mark: |  |
| Built-in notifiers automatically created after SLA creation | :cross_mark: | :check_mark: |  |
| Calendar definition | :check_mark: | :check_mark: | Unlike the 24-hour shifts in DC, a maximum shift in the cloud runs from 00:00 to 23:59. |
| Dynamic calendar selection via issue | :cross_mark: | :check_mark: |  |
| SLA fields | :check_mark: | :check_mark:* | *Cloud currently supports the **SLA Date**, **SLA Indicator**, **SLA Duration**, and **Dynamic Calendar** fields.<br>Since the functionality differs, please refer to the <u>[documentation](https://appfire.atlassian.net/wiki/spaces/TTSC/pages/2875654192/Custom+fields?atl_f=PAGETREE)</u> for full details. |
| SLA Panels | :check_mark: | :check_mark: |  |
| Permissions | :check_mark: | :check_mark: |  |
| SLA Reports | :check_mark: | :check_mark: |  |
| SLA Recalculation | :check_mark: | :check_mark: |  |
| Integrity Checker | :check_mark: | :cross_mark: |  |
| Settings | :check_mark: | :check_mark: |  |
| Import/Export | :check_mark: | :check_mark: |  |
| License Management | :check_mark: | :cross_mark: |  |
| Time to SLA preferences | :check_mark: | :check_mark: |  |
| Features in Project Settings | Customer Portal SLAs | :check_mark: | :check_mark: |  |
| Features in Workflow | Post function (Reset SLA) | :check_mark: | :check_mark: |  |
| Features in Dashboards | Gadgets | :check_mark: | ⚠️ | Currently, only `TTS - Periodic Met vs Exceeded SLA` is available in the cloud. However, a new gadget called `TTS - SLA/Assignee Performance Gadget` is now on the cloud. |
| Features in Issue Search | JQL Functions | :check_mark: | :cross_mark: |  |
| Features in Issue View | Issue Actions | :check_mark: | :check_mark: | In the cloud, you can [trigger Jira automation rules via notifiers](https://appfire.atlassian.net/wiki/x/kgVEVw). |
| SLA History | :check_mark: | :check_mark: |  |
| SLA Overview | :check_mark: | :cross_mark: |  |
| SLA Panel - SLA info | :check_mark: | :check_mark: |  |
| SLA Panel - Contract Extension | :cross_mark: | :check_mark: |  |
| Features in Non-GUI Access | REST API | :check_mark: | :check_mark: |  |
| Integrations | eazyBI | :check_mark: | :check_mark: |  |
| Automation for Jira | :check_mark: | :check_mark: |  |
| Better Excel Exporter | :check_mark: | :cross_mark: |  |
| Configuration Manager for Jira | :check_mark: | :cross_mark: |  |
| Theme Extension for JSM | :check_mark: | :cross_mark: |  |
| PowerBI Connector for Jira | :check_mark: | :cross_mark: |  |
| Dashboard Hub Pro (Charts, Reports, Time in Status for Jira) | :cross_mark: | :check_mark: |  |