---
title: Known Issues - 2026
slug: neurons-for-itsm-release-notes-enu-latest/known-issues-2026
createdAt: 2026-06-23T14:39:57.000Z
---

## Version 2026.3

Following is a known issue for release 2026.3:

| Problem ID | Description                                                                                                                                  |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| 108500     | For non-English locales, filtering CI records on the **Name&#x20;**&#x66;ield fails to return records assigned to the **Asset Type (None)**. |

## Version 2026.2

Following is a known issue for release 2026.2.5 Patch #5:

| Problem ID | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1998224    | When you create a Service Request through the Agentic AI agent, the **Total Incidents + SR's Created Using AI Agents&#x20;**&#x6D;etric on the AI Configuration Hub > Agentic AI > **Analytics&#x20;**&#x70;age is not updated. This occurs because Service Request forms are now opened as web pages instead of adaptive cards within the chat, and Service Requests created through this process are not tracked by the Service Request telemetry object. |

Following is a known issue for release 2026.2 Patch #4:

| Problem ID | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1966746    | Ivanti Service Management Portfolio UI V3 includes the Temporary UI Switcher, which allows administrators to change from Modern Layouts and Lists to the Classic UI. This functionality is available only in Modern Layouts configured as a top-level tab for users with the administrator role.<br />**Expected result:** Administrators can use the Temporary UI Switcher to access the Classic UI while working with Modern Layouts and Lists. Standard users continue to use Classic Forms without any change.<br />**Actual result:** The Temporary UI Switcher is available only to administrators in supported Modern Layouts and serves as a temporary migration aid. Full migration from Classic Analyst Forms to Portfolio UI V3 Forms is not currently supported.<br />**Workaround:&#x20;**&#x43;ontinue using Classic Analyst Forms for production environments until Ivanti provides a supported migration path to Portfolio UI V3 Forms in a future release. The Temporary UI Switcher can be used for evaluation and migration planning purposes only and is not intended as a permanent dual UI solution.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| 1971053    | When a user creates an incident or request offering using the modern page layout in Form Offerings, the matching panel displays related articles to help resolve the issue. If the user finds a resolution in one of these articles and click **Resolve&#x20;**&#x62;utton after entering details in all mandatory fields, the incident still remain in the **In Progress** state instead of moving to the **Closed&#x20;**&#x73;tate.<br />**Expected result:&#x20;**&#x54;he issue transitions from Work in Progress to Resolved when the Resolve action is performed and the mandatory field contains a valid value.<br />**Actual result:&#x20;**&#x54;he issue remains in the Work in Progress state and does not transition to Resolved, even though the mandatory field contains a value.<br />**Workarounds:**<br />**Option 1:** Make the mandatory field optional<br />1. From the **Configuration console**, go to **Build&#x20;**> **Business Objects**.<br />2. Click **Incident**, select **Business Rules**.<br />3. Enter mandatory field name, for example description in the **Search field names** only text box and search.<br />4. Toggle off the status button for **Required Rule for Incident.Symptom (Default)** rule.<br />**Option 2:** Configure a default value<br />5. From the **Configuration console**, go to **Build&#x20;**> **Automation Tools** > **Object Matching Lists**.<br />6. Select the object matching layout, for example - FAQ, Document Object Matching for Incident.<br />7. In the Preview window, click **Edit**.<br />8. Click **Add field**, enter field name, for example description in the **Field Name** and enter value in **Update with** column and then click **Save**.<br />9. Repeat same steps from step 4- 6 for other object name. |

## Version 2026.1

Following are the known issues for release 2026.1:

| Problem ID | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1723077    | In the Modern Layout Designer, the Use existing option currently supports Data Grid views only. Support for using existing Kanban and Gallery grids is under development. As a result, when you attempt to create a Kanban or Gallery view using an existing grid, the selection dropdown remains empty.&#xD;**Steps:**<br />1. Log in to the Modern Layout Designer.<br />2. Select an existing layout, or create a new layout.<br />3. Create a new view and select **Kanban** or **Gallery** as the view type.<br />4. Select **Use existing Kanban** views or **Use existing Gallery** views.<br />5. Observe the dropdown for selecting an existing view.&#xD;**Expected result:** The dropdown lists all existing views of the selected type (Kanban or Gallery).&#xD;**Actual result:** The dropdown is empty for Kanban and Gallery views.&#xD;**Workaround:** There is no workaround to reuse existing Kanban or Gallery views. However, you can create a new Kanban or Gallery view during view creation. |
| 1742668    | When you upgrade to Neurons to ITSM 2026.1 version, the Item dropdown displays a Rec ID instead of the item name when configuring list module options for the self-service page. This issue occurs when an existing configuration contains only a Rec ID and no item name. This behavior to support configurations from earlier releases and ensures backward compatibility.&#xD;**Steps:**<br />1. Upgrade to Neurons for ITSM 2026.1 version.<br />2. To set customized click, go to **Page designer** > **Options**, select list module with an existing Item that contains only a Rec ID.&#xD;**Expected result:** Display the expected item name.&#xD;**Actual result:** The dropdown displays the Rec ID instead of item name.&#xD;**Workaround:** Reselect the item in the dropdown and save the configuration. This action updates the configuration and restores the correct item name in the dropdown.                                                                                                    |
