Build richer alert workflows with full resolution context.

Alert-triggered workflows have always been able to act on what happened — but not on who handled it or when. There was no way to reference the responder who acknowledged or resolved an alert inside a workflow action, which meant follow-up automation had to leave that context out or look it up separately.

Acknowledged by, resolved by, and alert timeline are now exposed as Liquid variables in alert-triggered workflows. You can reference them directly in any workflow action that accepts template input — Slack messages, Jira tickets, status updates, or any custom action.

What’s included

{{ alert.acknowledged_by }} — the responder who first acknowledged the alert
{{ alert.resolved_by }} — the responder who closed it out
{{ alert.timeline }} — structured timeline data of status changes and key events

This unlocks workflows that can automatically attribute resolution to the right responder in follow-up tickets, include handler context in Slack status updates, or trigger downstream actions based on who handled an alert — without any manual lookup.

What else shipped

Improvements

On-Call

Alert sources can now be filtered by team, making it easier to find the right source in multi-team organizations.
Notification preferences now only display Slack as a paging option when Slack is connected to the organization.

Incident Response

The Related Incident field now shows the incident name on both the web UI and in Slack, instead of just the incident ID.
Opsgenie client rate limit handling has been improved for more reliable behavior during high-volume syncs.
Slack-triggered workflows are now gated by the organization’s Slack connection status, preventing errors when Slack is not connected.
Dashboard ownership can now be transferred to another team member.

API & CLI

On-Call

Fixed a bug where the GET /users endpoint returned schedule data across all organizations instead of only the requesting organization’s data.

Incident Response

Fixed an issue preventing incidents from being filtered by custom fields through the API.
Fixed deadlock errors on the FormFieldOptions endpoint that occurred during bulk delete operations.
Fixed API key permission options showing actions not available to the user’s role.

Fixes

On-Call

Fixed an issue where live mode view filters were not applying to alerts that arrived after the filter was set.
Fixed a permissions bug that allowed users without alert source access to view all alert sources.
Restored missing placeholder text in the notification and shadow dropdowns on the Schedules page.
Fixed a crash in call notification dispatch caused by Alibaba Cloud rate limiting errors.
Fixed an issue where Live Call Routing calls failed to escalate when the first responder declined the call.

Incident Response

Fixed Slack inactivity reminders appearing in channels for cancelled incidents.
Fixed status page posts intermittently using the internal incident title instead of the external one.
Fixed “Channel Not Found” errors when workflows ran in private Slack channels.
Fixed a 500 error on the forms edit page.
Fixed an issue where duplicating a workflow did not copy over sub-status conditions.
Fixed incident names being duplicated with an ID appended to the title.
Fixed a missing integration selector in the “Update Jira Issue” workflow action.
Fixed an “undefined variable TOKEN” error when using the OpenAI workflow action.
Fixed meeting transcription messages appearing out of chronological order.
Fixed MS Teams SSO login returning 404 when the Azure AD UPN domain differs from the user’s email domain.

Editor’s note: Atlassian is retiring Opsgenie, with end-of-life scheduled for April 2027—factor a migration path into any evaluation.