> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/release-notes/more-products/ai-sre.md).

# AI SRE

The release notes describe recent changes to Harness AI SRE.

{% hint style="info" %}
**ABOUT HARNESS RELEASE NOTES**

* **Progressive deployment:** Harness deploys changes to Harness SaaS clusters on a progressive basis. This means the features described in these release notes may not be immediately available in your cluster. To identify the cluster that hosts your account, go to your **Account Overview** page in Harness. In the new UI, go to **Account Settings**, **Account Details**, **General**, **Account Details**, and then **Platform Service Versions**.
* **Security advisories:** Harness publishes security advisories for every release. Go to the [Harness Trust Center](https://trust.harness.io/?itemUid=c41ff7d5-98e7-4d79-9594-fd8ef93a2838\&source=documents_card) to request access to the security advisories.
* **More release notes:** Go to [Harness Release Notes](/release-notes/release-notes.md) to explore all Harness release notes, including module, delegate, Self-Managed Enterprise Edition, and FirstGen release notes.
  {% endhint %}

<a href="https://developer.harness.io/release-notes/ai-sre/rss.xml" class="button primary small" data-icon="square-rss">Subscribe via RSS</a>

{% updates format="full" %}
{% update date="2026-11-01" %}

## November 2026 <a href="#november-2026" id="november-2026"></a>

**New Features and Enhancements**

* **Key Event Notifications Threaded Under the Incident Summary:** Key event notifications from the incident call now post as replies under the incident summary message in Slack instead of as top-level messages, which keeps the main incident channel readable during an active incident. The notifications are not also sent to the channel. This applies to every Slack channel that has an incident summary message, including the incident channel and channels connected through child orgs. If a channel has no summary message yet, the notification posts to the channel as before. No configuration is required.
  {% endupdate %}

{% update date="2026-10-01" %}

## October 2026 <a href="#october-2026" id="october-2026"></a>

**New Features and Enhancements**

* **Postmortem Draft at Incident Close:** When an incident closes, AI SRE gathers incident fields and timeline activity into an editable postmortem on the incident and posts it to Slack. Admins can define section titles and guidance in a postmortem template so the generated draft follows your SRE or compliance format; default sections are used when no template is set. You can also attach a postmortem meeting and regenerate the draft with its transcript, so conclusions from the review become part of the written postmortem.
* **Action Item Capture During Incidents:** Say or type "action item" during an incident and AI SRE captures what follows as a tracked action item. A reaction in Slack confirms whether the item was captured or needs review. AI SRE also detects follow-ups from incident conversation, meeting transcription, and notes, then deduplicates them in the incident action list, including assignees and due dates when people state them.
* **Live Root Cause Theories and Ask AI in Context:** The Root Cause panel and investigation view show AI SRE's evolving analysis, and the theory record updates when responders state a root cause or rule out a theory in incident messages. You can open Ask AI from the alerts list or an alert, the incident list or an incident, and the changes list, and the items on screen are supplied as context. The investigator also considers incident-related alerts, recent events from connected change sources, and similar closed incidents. Similar incident search covers incidents closed after the capability was enabled, and recent change evidence requires connected change sources. Go to [Use Investigator Agent Pipelines](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-incident-responders/use-ai-agents/investigator-agent-pipelines/README.md) to choose which runbooks the investigator can run with **Expose to AI**.
* **SLO Pages and Settings Generally Available:** SLO pages and settings are now generally available in AI SRE as Harness SRM sunsets. Go to [Harness SLO Integration](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-administrators/set-up-integration-management/monitoring/harness-slo/README.md) to configure SLO tracking.
* **Nested Conditions, CEL, and For Each in Runbooks and Rules:** Runbooks, alert rules, transforms, and paging rules support nested AND/OR conditions or CEL expressions, and runbook Conditional steps can branch on the result. A **For Each** step runs its child steps for every item in a JSON list or template, so one runbook can work through affected hosts or services. Go to [Use CEL in Runbook Actions](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-administrators/set-up-runbook-management/workflows/use-cel-runbook-actions/README.md) to write conditions.
* **Launch a Runbook from Slack and Edit Workflows as YAML:** Give a runbook a Slack slug, then run `/harness run {slug}` in Slack to start it. In the runbook builder, switch the **Workflow** tab between the visual builder and editable YAML. Go to [Execute Runbooks](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-incident-responders/respond-to-active-incidents/execute-runbooks/README.md) to run a runbook during an incident.
* **Page Sent Runbook Trigger:** A **Page sent** event can start a runbook based on channel, escalation policy, or responder, and the runbook can send a configured email update as part of the workflow. Go to [Create a Trigger](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-administrators/set-up-runbook-management/triggers/create-trigger/README.md) to set one up.
* **Create Incident and Create Alert Pipeline Steps:** A **Create Incident** step in a Harness pipeline can fill in the title, severity, service, environment, description, and incident type from pipeline expressions. It can attach the execution context, page on-call, name an incident commander, and include other impacted services. A **Create Alert** step records the title, status, priority, service, environment, and description in AI SRE, and passing an existing alert ID updates that alert as the pipeline progresses. Go to [Harness Pipelines](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-administrators/set-up-integration-management/cicd-change/harness-pipelines/README.md) to connect your pipelines.
* **Page Without an Incident:** Give a service its own paging webhook or email address so monitors and jobs can page on-call directly. Runbooks can include a Harness paging action, the **Page** action on **On Call** and **Overview** notifies a person before an incident exists, and responders can cancel an active page from the incident responders table. Paging before an incident requires **On Call** to be enabled.
* **Mobile Paging Through Pushy:** The mobile app can use Pushy alongside Firebase for pages and shift reminders, which gives supported devices a delivery path in countries where Google services are blocked.
  {% endupdate %}

{% update date="2026-09-01" %}

## September 2026 <a href="#september-2026" id="september-2026"></a>

**New Features and Enhancements**

* **Archive Incidents and Alerts:** You can now archive resolved incidents and alerts to declutter your active views.
* **Effective Start Time for On-Call Schedule Changes:** When you change an on-call schedule, you can now choose when the change takes effect, with **now** as an option. Go to [Configure On-Call Schedules](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-administrators/set-up-on-call-management/create-oncall-schedules/README.md) to update a schedule.
* **Protected Escalation Policies:** AI SRE now blocks deleting an escalation policy that an alert rule still references, so alert rules no longer break silently. Go to [Define Escalation Policies](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-administrators/set-up-on-call-management/define-escalation-policies/README.md) to manage policies.
* **xMatters Event Runbook Actions:** Runbooks can now create an xMatters event and close it with native runbook actions, following the same pattern as the Jira, ServiceNow, and PagerDuty actions. Go to [xMatters](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/incident-management/xmatters/README.md) to use the actions in a runbook.
* **Microsoft Teams Delegate Connector:** AI SRE now supports a delegate-based connector for Microsoft Teams. Go to [Microsoft Teams](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-administrators/set-up-integration-management/communication/microsoft-teams/README.md) to connect it.
* **Usergroups and Channel Names in Invite Users to Slack Channel:** The **Invite Users to Slack Channel** action now accepts Slack usergroup IDs and channel names, not only individual user IDs. Users who are already in the channel no longer block the rest of the invite.
* **Deploy Event Context in the Runbook Data Picker:** Runbook authors can now select deploy event fields in the data picker.
* **Pull Requests and Services in Postmortems:** Pull requests now create activity records that you can mark as related activity in a postmortem, and activities can be linked to the services they affected. You can also undo a root cause theory determination if it was marked by mistake.
* **Ask AI for Alerts:** The Ask AI conversational query capability that was available on the incident page is now available on the alerts page, so you can ask questions about alerts the same way you do for incidents.
  {% endupdate %}

{% update date="2026-08-01" %}

## August 2026 <a href="#august-2026" id="august-2026"></a>

**New Features and Enhancements**

* **Jira Service Management Connector:** AI SRE now has a native connector for Jira Service Management. Go to [Jira Service Management](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-administrators/set-up-integration-management/ticketing-itsm/jira-service-management/README.md) to connect it.
* **ServiceNow Incident Fields from ServiceNow Metadata:** The native ServiceNow runbook actions now load incident field metadata and dropdown options directly from ServiceNow, so options match your ServiceNow configuration instead of a fixed list. Go to [ServiceNow](https://github.com/harness/harness-developer-hub/tree/main/docs/operations/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/ticketing/servicenow/README.md) to use the actions.
* **Incident Search Through MCP:** Incident embeddings are now exposed through MCP search, so MCP-based agents and tools can search AI SRE incident data.
* **Alert Acknowledgement Records Timing:** Acknowledging an alert now sets the Responder and Mitigation timing fields, so response metrics reflect who responded and when.
* **Webhook HMAC Signature Verification:** Webhook endpoints now support optional HMAC signature verification, so only authorized sources can trigger webhook-driven workflows in AI SRE. Admins configure a shared secret through Harness Secret Manager and turn verification on per webhook source, including Slack's signature format.
* **Acknowledge Incidents and Alerts from Mobile Push Notifications:** On the mobile app, you can now acknowledge an incident or alert directly from the push notification without opening the app.
  {% endupdate %}

{% update date="2026-07-01" %}

## July 2026 <a href="#july-2026" id="july-2026"></a>

**New Features and Enhancements**

* **SLO Management Migrated from SRM:** AI-SRE now manages SLOs independently from Harness SRM, with a native SLO experience including listing, details, create/edit screens, and integrated alerts. The migration preserves all existing SLO configurations while providing a streamlined interface designed for incident response workflows. SLOs created in AI-SRE automatically generate alerts that feed into the incident management system. Navigate to **On-Call > SLOs** to manage your service level objectives. Go to [Harness SLO Integration](/ai-sre/ai-sre-for-administrators/set-up-integration-management/monitoring/harness-slo.md) to configure SLO tracking.
* **Worker Agent and Pipeline Outputs in Root Cause Analysis:** Extend the data the AI Investigator reasons over during root-cause analysis. A runbook flagged as exposed to AI runs during an investigation, either triggered automatically or executed with a human in the loop, and the output of its actions is fed into the RCA interpretation. Within a runbook you compose out-of-the-box actions and Harness Pipeline executions, including worker agents, so if a task can run in a pipeline, such as pulling logs, querying an internal service, or reading source to trace an error, its results can enrich the investigation. This is an Early Access feature; contact your Harness representative to enable it. Go to [Use Investigator Agent Pipelines](/ai-sre/ai-sre-for-incident-responders/use-ai-agents/investigator-agent-pipelines.md) to configure a runbook exposed to the AI Investigator.
* **Ask AI SRE:** Query incident data, investigation context, and on-call status through a conversational AI interface. Type natural language questions about incidents, service health, or on-call schedules and get instant answers powered by AI. Access Ask AI SRE from the main navigation or within incident details.
* **On-Call Schedule Sharing:** Share on-call schedules with stakeholders via email digest or Slack command. Schedule owners can configure automated daily or weekly email digests showing who is on call for each schedule, and users in Slack can run `/harness oncall` to see current on-call assignments across all schedules they have access to. Configure email digests under **On-Call > Schedules** by selecting a schedule and navigating to the **Sharing** tab. Go to [Configure On-Call Schedules](/ai-sre/ai-sre-for-administrators/set-up-on-call-management/create-oncall-schedules.md) to set up schedule sharing.
* **Unified Data Platform Integration:** AI-SRE data is now integrated into the Harness Knowledge Graph and available via MCP (Model Context Protocol) for cross-module analytics and insights. Incident and alert data can be queried alongside deployment, CI/CD, and infrastructure data for comprehensive engineering intelligence. This enables correlation across the platform and powers custom analytics workflows. Contact your Harness representative for access to UDP data sources.
* **Custom Dashboards for Incident Analytics:** Build custom dashboards using Harness Platform Dashboards with AI-SRE incident and alert data. Create tailored reporting views with incident volume trends, MTTR metrics, alert-to-incident ratios, and service health indicators. Dashboards support filtering by service, severity, time range, and custom dimensions. Navigate to **Platform > Dashboards** to create custom incident analytics dashboards. Go to [Platform Dashboards](/harness-platform/use-harness-platform/harness-dashboards/dashboard-standard/overview.md) to get started.
  {% endupdate %}

{% update date="2026-06-01" %}

## June 2026 <a href="#june-2026" id="june-2026"></a>

**New Features and Enhancements**

* **Selective On-Call Sync:** You can now import on-call configuration selectively from PagerDuty, OpsGenie, and xMatters by choosing specific services (PagerDuty) or groups (OpsGenie, xMatters) rather than importing an entire account. A preview step shows which users, teams, schedules, and escalation policies already exist in Harness before you commit, and the sync runs as a resumable, cancellable background job that stays idempotent on retry. Matched users are invited and on-call roles are auto-assigned during the sync, and a dedicated sync history view tracks each run's results. Navigate to **On-Call > 3rd Party Sync** to import from a connected provider. This feature is gated behind the `IR_ENABLE_SELECTIVE_SYNC` feature flag and enabled per account; contact Harness to have it enabled for your organization. Go to [Configure On-Call Schedules](/ai-sre/ai-sre-for-administrators/set-up-on-call-management/create-oncall-schedules.md) to set up on-call schedules.
* **Duplicate Runbook:** You can now duplicate an existing runbook from the runbook menu. Selecting **Duplicate** creates a full copy with all chain items, action configurations, and metadata preserved, then automatically navigates to the newly created runbook so you can rename and adjust it. This is helpful for building variations of a proven runbook without rebuilding from scratch. This feature is gated behind the `IR_DUPLICATE_RUNBOOK` feature flag. See [Create a Runbook](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/create-runbook.md) for details.
  {% endupdate %}

{% update date="2026-05-01" %}

## May 2026 <a href="#may-2026" id="may-2026"></a>

**New Features and Enhancements**

* **Rotation-Level Escalation Targeting:** Escalation policies can now target a specific rotation within a schedule, in addition to entire schedules and individual users. When building an escalation level, a **Rotations** section appears alongside **Schedules** and **Users**, listing every rotation labeled with its parent schedule (for example, "IT West Critical Rotation (IT West schedule)"). All three targeting modes can be combined across different levels of the same policy, and if a referenced rotation is later deleted or renamed, that escalation level is skipped gracefully so escalation continues to the next level. Configure under **On-Call > Escalation Policies**. Go to [Configure Escalation Policies](/ai-sre/ai-sre-for-administrators/set-up-on-call-management/define-escalation-policies.md) to configure rotation-level escalation targeting.
* **CEL Expression Engine:** AI SRE now supports [Common Expression Language (CEL)](https://github.com/google/cel-spec) as a full expression engine alongside Mustache templates. Write dynamic conditions using regex matching, datetime formatting, list comprehensions, and math operations in alert rule conditions, runbook trigger conditions, webhook advanced mapping conditions, and inline within runbook action field values using `${{ }}` syntax. A unified conditional builder provides consistent editing with syntax highlighting and inline validation across all expression surfaces. Go to [Create a Trigger](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/triggers/overview.md) to learn about CEL expression syntax.
* **Google Chat Bidirectional Sync and Native Actions:** The Google Chat integration now supports bidirectional timeline mirroring. Messages posted in the AI SRE UI automatically appear in the linked Google Chat space, and Google Chat messages are ingested into the incident timeline via webhook. New native runbook actions allow you to **Create Google Chat Space** and **Add Members to Space** directly from runbook automation. Go to [Google Chat Integration](/ai-sre/ai-sre-for-administrators/set-up-integration-management/communication/google-chat.md) to configure bidirectional sync.
* **Slack Summary Modal:** The incident summary in Slack now opens in a modal dialog instead of inline, providing a cleaner reading experience and reducing channel noise.
  {% endupdate %}

{% update date="2026-04-01" %}

## April 2026 <a href="#april-2026" id="april-2026"></a>

**New Features and Enhancements**

* **AI-Native Post-Mortem Generation:** AI SRE now auto-generates a structured post-incident review when an incident is closed. The AI synthesizes incident metadata, timeline events, RCA theories, and notes into six sections (Summary, Impact, Root Cause, Resolution, Insights, Lessons Learned). View the generated post-mortem on the **Postmortem** tab of closed incidents. Manual regeneration is also available via the incident detail page. Go to [Resolve and Review Incidents](/ai-sre/ai-sre-for-incident-responders/respond-to-active-incidents/resolve-and-review.md) to review the post-mortem workflow.
* **Real-Time Action Item Detection:** AI SRE now detects action items in real-time during active incidents from Slack chat messages, meeting transcriptions, and incident notes. Each detected item includes a description and the name of the person who committed to it. Detected items appear in the **Action Items** pane and are deduplicated against existing items. Go to [Create and Track Action Items](/ai-sre/ai-sre-for-incident-responders/respond-to-active-incidents/create-and-track-action-items.md) to configure action item detection.
* **ServiceNow Change Correlation in AI Investigator:** The AI RCA Investigator now automatically polls ServiceNow change records and correlates them to active incidents with no additional configuration required beyond an existing Harness ServiceNow connector. Change data appears alongside deploy events and code changes in the Investigator panel. This is the first external change signal source in the AI Investigator. Go to [Use RCA Change Agent](/ai-sre/ai-sre-for-incident-responders/use-ai-agents/rca-change-agent.md) to configure change correlation.
* **Incident Status Updates:** Incident commanders can now send structured status updates to stakeholders subscribed to impacted services. Navigate to an active incident and click **Status Update** to compose a pre-populated email with incident context. Recipients are resolved dynamically from all impacted services' subscriber lists. Configure subscribers on the **Subscribers** tab of any service in the [Service Directory](/ai-sre/ai-sre-for-administrators/set-up-on-call-management/integrate-service-directory.md).
* **Google Chat Integration:** AI SRE now supports Google Chat for incident collaboration. Teams using Google Workspace can create incident spaces, post updates, and collaborate in real-time. The integration uses GCP Pub/Sub for reliable message delivery. Configure under **Integrations** with a one-time GCP project and Pub/Sub topic setup.
* **Runbook Slug Commands in Slack:** On-call responders can now trigger runbook automations directly from Slack using short slug commands. Type `/harness run <slug>` in an incident channel to execute a runbook instantly. Configure a slug (3-15 characters) on any runbook under **Triggers**. Requires Slack authentication. Use `/harness run` without a slug to list available commands. Go to [Use Slack Commands](/ai-sre/ai-sre-for-incident-responders/slack-commands.md) to set up slug commands.
  {% endupdate %}

{% update date="2026-03-01" %}

## March 2026 <a href="#march-2026" id="march-2026"></a>

**New Features and Enhancements**

* **ServiceNow Native Actions:** Runbooks now include native ServiceNow actions for creating incidents, updating incidents, and adding comments, without requiring custom webhook configuration. Fields are dynamically retrieved from your ServiceNow instance based on your connector. Configure a ServiceNow connector under Project Settings -> **Connectors**, then use the **Create ServiceNow Incident**, **Update ServiceNow Incident**, and **Add ServiceNow Comment** actions in your runbooks.
* **User-Defined Webhook Templates:** You can now save webhook configurations as reusable templates and select them when creating new integrations. Configure a webhook once, click **Save as Template**, and reuse it across future webhooks. Templates appear in the **Select Payload Template** dropdown grouped under **System Templates** and **Custom Templates**. Templates are organization-scoped and use copy-on-write — changes do not propagate to existing webhooks. Go to [Configure Webhooks](/ai-sre/ai-sre-for-administrators/set-up-alert-management/webhooks/overview.md) to configure webhook templates.
* **Named Alert Rules:** Alert rules now support custom display names, making it easier to identify and manage rules across your organization. Set a name when creating or editing an alert rule under **Alerts > Alert Rules**.
* **Active Pages View:** On-call users can now view all currently active pages from the **On-Call > Shifts** sidebar. The active pages table shows page status, assigned responders, escalation progress, and acknowledgment state, giving on-call managers a single view of all in-progress pages.
* **Documentation Restructured for Admins and Responders:** AI SRE documentation has been reorganized into separate paths for [administrators](/ai-sre/ai-sre-for-administrators/get-started/overview.md) and [incident responders](/ai-sre/ai-sre-for-incident-responders/onboarding-guide-users.md). Admins get a streamlined path through alert configuration, runbook automation, on-call schedules, and integrations. Responders get a new task-oriented [Users](/ai-sre/ai-sre-for-incident-responders/respond-to-active-incidents/acknowledge-and-triage.md) section covering incident creation, triage, runbook execution, action items, and the [mobile on-call experience](/ai-sre/ai-sre-for-incident-responders/handle-on-call/oncall-mobile-app.md).
  {% endupdate %}

{% update date="2026-02-01" %}

## February 2026 <a href="#february-2026" id="february-2026"></a>

**New Features and Enhancements**

* **Service Subscriptions and Status Updates:** Users can now subscribe to services in the [Service Directory](/ai-sre/ai-sre-for-administrators/set-up-on-call-management/integrate-service-directory.md) to receive automated status updates during incidents. Navigate to **On-Call > Service Directory**, select a service, and use the **Subscribers** tab to add users or teams. Incident commanders can send status updates from the incident detail page with recipients auto-populated from impacted service subscribers.
* **On-Call Notification Rules (SMS, Push, Voice):** On-call notification rules now support SMS, push notifications, and voice calls in addition to email and Slack. SMS and voice call support is currently available for US phone numbers, with additional regions enabled within 21 days of request. Push notifications via the mobile apps are available globally. Configure your contact methods under **On-Call > Contact Settings**.
* **Harness AI SRE Mobile App:** Native mobile apps are now available on the [App Store](https://apps.apple.com/us/app/harness-on-call/id6753579217) and [Google Play](https://play.google.com/store/apps/details?id=com.harness.aisre). Responders can acknowledge, escalate, and resolve incidents and alerts directly from their phone, with critical alert override for Do Not Disturb mode. See the [Mobile App Guide](/ai-sre/ai-sre-for-incident-responders/handle-on-call/oncall-mobile-app.md) for setup instructions.
* **Escalation Policy: Individual User Management:** Escalation policies now support targeting individual users in addition to groups and schedules. Configure under **On-Call > Escalation Policies**.
* **Customizable Incident Severity and Alert Priority:** Incident severity levels and alert priority mappings are now fully customizable to match your organization's standards. Configure under **On-Call > Settings**.
* **OpsGenie Migration Tooling:** Import schedules, escalation policies, and user configurations directly from OpsGenie. Accessible under **On-Call > Settings > Import**.
* **PagerDuty Migration Tooling:** Import schedules, escalation policies, and user configurations directly from PagerDuty. Accessible under **On-Call > Settings > Import**.
* **Jira Dynamic Fields Integration:** The new **Create Jira Ticket V2** and **Update Jira Issue V2** [runbook actions](/ai-sre/ai-sre-for-administrators/set-up-runbook-management/integrations/ticketing/jira.md) dynamically retrieve available fields based on the selected Jira project and issue type, replacing the previous static field configuration. Fields render with appropriate input types including multi-select for array fields. A manual key-value mode is available when the issue type is set dynamically using Mustache expressions.

{% hint style="info" %}
On-call is currently optimized for teams using AI SRE's incident response and alert management workflows. Direct integrations with third-party observability tools (e.g., Datadog) that enable automatic paging workflows between those tools and AI SRE on-call are planned for a future release.
{% endhint %}

**Fixed Issues**

* Fixed invalid Jira ticket URLs not being rejected, which caused downstream Slack integration failures.
* Fixed custom field persistence issues after save in Jira runbook actions.
* Fixed multi-select and labels fields rendering as single-select in Jira runbook actions. Array-type fields (labels, components, multi-select custom fields) now render correctly.
  {% endupdate %}
  {% endupdates %}

{% @harness-feedback/feedback module="release-notes" pagePath="release-notes/ai-sre" %}