---
title: "Release notes 12.0.0"
canonical: "https://support.appfire.com/space/TTS/3659956263/Release%20notes%2012.0.0"
format: markdown
---
**Release date**: 9/15/2026

This page outlines the updates included in this release of Time to SLA for Jira Data Center.

**Jira compatibility**:

- 12.0.0 → 11.0.0 - 11.3.11

---

# What's new

## SLA search index V2

Time to SLA now uses a new search index schema for SLA JQL functions, sorters, date fields, and related dashboards and gadgets. The new schema uses a fixed set of index fields and per-SLA search slots, improving compatibility and performance with Jira 11 search backends, including OpenSearch.

> ⚠️ **Required action after upgrade**
> ⚠️ 
> ⚠️ Run a full Jira issue reindex after upgrading (**System** > **Indexing** > **Re-index**).

Until the reindex completes:

- The app remains in dual-read compatibility mode: it writes V2 index data while search still uses legacy V1 index data for issues that have not been reindexed yet.
- SLA search may return incomplete or incorrect results.
- There will be a warning banner in Time to SLA configuration pages if the index migration hasn’t completed yet.

After a successful full issue reindex:

- The app switches to V2-only search mode automatically.
- SLA JQL functions, sorters, and SLA-based gadgets use the new index format exclusively.

## Improvements

- Reliable SLA state, duration, date, and sort JQL on Jira 11.
- Fixed-cardinality index fields, with no per-SLA dynamic schema registration.
- Dual-read migration path from legacy V1 tokens during upgrade.

---

# Bug fixes

The following bugs are fixed in this release:

- Fixed an issue during Jira Cloud Migration Assistant (JCMA) migrations where SLA records could be assigned null IDs.
- Fixed an issue during Jira Cloud Migration Assistant (JCMA) migrations where legacy SLA data was not correctly matched to issues, causing some issue SLAs to be skipped from the migration batch.
- Fixed an issue on Jira 11 where SLA stop conditions did not correctly account for comment visibility, causing internal comments to stop an SLA that should only stop on a public comment.

---

---