---
title: "Release notes 17 February 2025"
canonical: "https://support.appfire.com/space/TTS/1759838353/Release%20notes%2017%20February%202025"
format: markdown
---
> Macro (aura-html)

**Release date**: 2/17/2025

Our team is thrilled to announce the latest release of Time to SLA for Jira Cloud.

---

## Enhancements

### Incoming webhook changes implemented

We've updated the Incoming Webhook functionality in Time to SLA to align with Atlassian’s upcoming security changes.

Atlassian is updating how incoming webhook triggers are routed. Any automation rules created before January 28, 2025, will continue to work until May 30, 2025, but must be migrated to the new endpoint to remain functional beyond this date.

> 📝 If you use incoming webhooks in your automation rules, we strongly recommend reviewing and updating them as needed.

We’ve updated our SLA Notification configuration to support this transition to include a **Automation Webhook Secret** section. From now on, when creating a notification that will trigger a Jira automation rule, you must provide this information. 

![Time to SLA release notes February 2025 showing updated SLA interface](media://cd259663-aa8b-4325-99f1-497f4f698320)

> ✅ For more information, refer to the [documentation](https://appfire.atlassian.net/wiki/spaces/TTSC/pages/1464075666).

## Bug fixes

The following bugs are fixed in this release:

- Previously, when modifying an SLA field condition from 'is set' to 'changed to', the condition was automatically set to 'is equal to', which was unintended behavior. Additionally, when scrolling down, the user selection area was not visible. This issue has now been fixed.

---

---