Problem There's no way to display milestones that apply across the entire Gantt independent of the task hierarchy. Tying milestones to task rows means they disappear when rows collapse, and sibling-row workarounds are visually indistinguishable from real content rows.

Requested Behavior A pinned milestone band rendered above the task rows, below the timeline header, that:

• Stays visible regardless of row collapse state
• Scrolls horizontally with the timeline but not vertically with tasks
• Accepts milestone objects with date, label, color, and type
• Supports multiple milestones on the same band (stagger or tooltip on hover)

Use Case In our publication planning workflow, study-level dates (Data Lock, Embargo Lift, Interim Analysis) are reference points that need to be visible while scrolling through 20–50 task rows. These don't belong to any single task — they're plan-wide context.

Proposed API

globalMilestones: [
  { date: new Date("2026-03-01"), label: "Data Lock", color: "#F58010" },
  { date: new Date("2026-05-15"), label: "Embargo Lift", color: "#20B34A" },
],
showGlobalMilestoneBand: true,
globalMilestoneBandHeight: 32

Hi Team,

I would like to request a way to prevent a responsive Grid from displaying an input when the screensize/container is shorter.  Perhaps, decreasing the buttonCount automatically instead of displaying the input may be a reasonable alternative.  This would be better than setting the pageable.responsive configuration to false.  

Thank you!

Hi Team,

Background

Kendo controls column width exclusively via <colgroup><col width="Npx"> attributes. CSS min-width on <col> is not supported by browsers (per spec). There is no minWidth property in the column configuration API. When a column has no explicit width set, it can collapse to near-zero width when the grid container is narrow - making content completely unreadable. This request excludes the columns.minResizableWidth as resizable is necessary with this configuration.

Request

We need the following to work generically across all grids without per-instance config changes:

1. Column minWidth API

columns: [
  { field: "name", title: "Name", minWidth: 150 }  // ← requested or it would be great if this min width we can apply at global level
]

Where minWidth is respected even if no width is specified, and is not overridden if an explicit width larger than minWidth is set else the global min width of 150px should be considered.

2. Grid-level minWidth config

$("#grid").kendoGrid({
  minWidth: 1000  // ← requested: grid never renders narrower than this or columnCount * default columns global width (150px) whichever is higher
});

Or ideally computed automatically as Math.max(1000, columns.length * defaultMinColWidth).

Hi Team,

What we're looking to achieve, is that when the page/grid enters edit mode, ALL fields in the grid should immediately become editable fields. This would help prevent the user from having to click on every cell to edit first, and the user would have a direct view of all fields actually being editable, make their changes, hit the save button on the page, and save everything at once.

Currently it's difficult for the user to actually know which fields they can edit, as they have to click a cell before it becomes editable.

Thank you!

The horizontal space between all OrgChart nodes on the same level is one and the same and it is equal to the horizontal space needed to show the child nodes of the parent with most child nodes. It is represented by the red squares on the image below. This results in excessive empty horizontal space between nodes with no child nodes or no visible child nodes.

This may be observed on the following Dojo runner. Currently the OrgChart has empty space between the first level nodes, and also there is empty space after the last node:

Suggested behavior:
There is no empty horizontal space between nodes on the same level - highlighted in yellow on the image above. In the above scenario, there should be no empty space between the first level's second and third node and no space after the third node, which may be observed, when the first node has no expanded child node:

Hello,

We would like to request this feature to expand on a Grid components Options.

Provide a built-in way for end-users to redefine or rename a Grid column's title directly through the user interface. Currently, if a user wants to change a column header from "Title1" to "Title2”, developers must write significant custom jQuery to modify the DOM or update the column via set options.

This is a functional request from our users, that we would like to provide for them.

Thanks,
John

Hi Team,

I would like to ask for a built-in Kendo UI implementation to import Excel files into the Kendo UI Grid.  

Thank you!

Hi Team,

I would like to ask for virtualization for the Kendo UI Scheduler when there is no grouping.  

Thank you!

Hi Team,

I would like to request adding the EventsPerDay configuration for the Week view. 

Thank you!

I realize this has been covered by this workaround in the past, but the need to write extra code for moving the column back to the original position makes this seem a bit "hacky" and most importantly, the user experience of being allowed to drag the column in the first place just to see it jump back seems wrong.

The good news is that the kendoGrid already has a mechanism for preventing the columnReorder event from getting fired in the first place! The bad news is that it only happens for columns that have either of these 2 classes ["k-group-cell, "k-hierarchy-cell"]

My request is to have a configuration option that enforces that same behavior for specific columns as:

1. Add a "reorderable" flag to be set as part of the column configuration (set it to false for those we want to keep in place)

2. This flag will set a class on those columns the same way it works for columns with "k-group-cell" or "k-hierarchy-cell" classes, so the event can be prevented.

There is one important caveat to consider with this approach: Only columns at the front and the back of the grid can be locked in place, so there needs to be validation to prevent having non-reorderable columns among reorderable ones.

I am currently using the ANDI accessibility tool and have encountered an accessibility issue with the tooltip icons across my application.

The tool reports an "Aria-Hidden Alert" stating: "Element is focusable but has or is contained by [aria-hidden = true]."  The tool also reports as "Keyboard Access Alerts" which states" "Focusable element is not in keyboard tab order; should it be tabbable"?

The HTML for these elements shows aria-hidden = true and focusable = false. I believe the focusable attribute should be set to true.

I have attempted to resolve this using JavaScript to directly removing aria-hidden = true and changing focusable to true.  However, there is no built-in configuration in Kendo UI for ASP.NET MVC to customize these accessibility attributes for tooltip icons therefore it didn't work.

Can you make the icons customizable?

I am including a screenshot of the code.

We use the KendoUI for jQuery framework in the enterprise SaaS application we create. Giving our clients access to their data and being able to provide a mechanism where a client could build out some of their own functionality on our Saas platform (ie accessing the Data, webservices etc) is highly desirable.

Our front end is based on a MicroUI approach, so if the client can vibecode building a new microUI, the UI experience with the other microUI we provide would be seamless. Examples might be: Create a Scheduler view showing all the European Holidays in 2026, or create a grid view populated with all the customers who have not transacted in 2025 and show their linkedin link/profile.

We can easily wrap any vide coded application into our application now using the microUI approach, but what we dont get is the same look and feel, themes and components being used. It is this we are looking to solve.

In the OData v4 transport, batch submit treats a top-level HTTP 200 response as success, even when one or more operations fail. This is due to how the changesets function.

The parseBatchResponse  function, which is called by the success callback belonging to the submit function of your OData v4 transport, as well as further processing in the same success callback. No attempt is made at handling anything other than responses having status codes [200... 299].

Please enhance batch handling so inner change set failures trigger explicit client error handling.

Add grouping option to the TaskBoard - multiple rows showing rows for separate projects/initiatives and cards with related tasks for each one. 

The row idea is seen at https://dhtmlx.com/docs/products/dhtmlxKanban/.

User want to drag the series point as well as series line(whole series line) in any direction, so the user can move the series where he want, please refer the below URL, where user can move the series point in vertical direction only, likewise the user want to drag the series point as well as series line in any direction, so he can set the threshold  limit where he want by using the custom series and analysis the chart against his threshold limit

http://jsfiddle.net/SpaceDog/QsKaJ/1/

Hi!

I am using the Kendo-UI Diagram widget to display relationships between items, that cannot be changed directly. I.e. I do not want users to be able to modify the diagram on their own. Unfortunately, I was not able to completely prevent modification of the diagram via its options.

For instance, I have set editable.remove to false. This prevents removing items already present at the widget's creation time, but it does not prevent removing items added later via diagram.addShape().

There are also several keyboard shortcuts like Ctrl+C (copy), Ctrl+V  (paste), Ctrl+X (cut) and Ctrl+D (duplicate) that I would like to turn off.

The only solution I have found so far is blocking the corresponding keyboard events and preventing their default behavior, but this seems more like a hack than a solution.

What do you suggest? 

Currently, the Kendo UI Toolbar supports adding icons to items by setting the "icon" property as documented here. However, only Kendo's own icons are supported.

In other widgets (like the Grid), adding custom icons (to a toolbar!) is already possible by specifiying an icon class.

However, if you wanted a third-party icon (or one of your own) directly to a standalone Toolbar, you would need to create a whole new template from scratch or replace the DOM element after rendering or use some hacky approach like demonstrated in this DOJO. While the first one means a lot of work, the latter ones are both not very stable.

Therefore, I propose to extend the icon support for Toolbars in general. I can think of two different solutions:

1. Let the developer specify an icon class (like in the Grid) that is then written into the DOM.
2. Let the developer specify some sort of "content template" that is displayed e.g. in a button or a splitButton. This way any content may be displayed in a toolbar item and this also allows for more complex and customized styling regarding the layout of e.g. icon and text.

I created a forum post and it was suggested that I create a feature request for improved Kendo Grid keyboard accessibility when the grid contains locked columns and/or clickable elements such as buttons, links, and input boxes. I noted the following issues that I feel should be supported without having to write a bunch of workarounds or create a poor user experience for regular (mouse and keyboard) users. 

This is an urgent concern because many of our clients are requiring our site to meet accessibility standards and with the heavy use of Kendo grids in their current state, it does not seem to.

I have a grid with 2 locked columns with a button in the first column and a hyperlink in the second column, the other columns just have text. I set navigatable to true. None of my fields are editable.

Here is a dojo: https://dojo.telerik.com/KUcMekCh

When the user tabs to the grid, they first get the search bar in my custom grid toolbar. Next they tab to the button (which happens to be a bootstrap dropdown menu but I don't think that is relevant). Here is where the issues start:

1. They then hit tab again and sometimes are taken to the hyberlink while other times they are taken to the next row, skipping column 2's hyperlink. 
2. The grid does not always enter Kendo's navigation mode. When it doesn't, there is no way for the user to interact with the column header which has the sort and tooltip buttons in it.
3. When they get to the bottom of the grid, the locked side will scroll vertically but the unlocked side remains in place, causing the rows to be misaligned.
4. When an input cell is in the unlocked portion of the table, the user has to tab through the entire list before getting back to editing the input for a row. This isn't logical.
5. I worry that if there were editable cells, which some of my grids have, the user won't be able to tab to the next editable cell and instead will be forced to navigate through every cell. I don't want to make it more difficult for a normal user in order to accommodate a keyboard only user so there needs to be a way for both to work well.
6. Often the focus ends up on the unlocked table which attempts to put a blue outline around that, however, the outline isn't fully visible since that is inside of a scrollable div.
7. You can click into a cell with navigatable set to true and then use the navigation but that doesn't work for a keyboard only user.
8. When navigatable is not turned on, the user cannot scroll vertically if they tab to the table.